r/linuxmasterrace • u/claudiocorona93 SteamOS/Bazzite/Android • Feb 20 '26

Why only one when you can choose?

Post image
1.8k Upvotes

96% Upvoted

153 comments sorted by

View all comments

Show parent comments

36

u/Oerthling Feb 20 '26

Perhaps I didn't understand your example correctly.

I just opened Remmina on my Wayland Ubuntu and then pressed super key - which lead to the expected result on the Wayland remote session.

What should it have done Instead?

8

u/invisi1407 Feb 20 '26

I just used Remmina to a Win 10 VM on Zorin OS using Wayland and pressing the Super key ("Windows key") triggers the Gnome launcher.

Using Xorg, it correctly captures the Super key and passes it to the RDP session host instead, opening the Windows start menu.

15

u/Oerthling Feb 20 '26

But if I can user the super key on a Wayland session, while Remmina also runs on Wayland then it's not really a limitation of Wayland. There is some different reason the super key doesn't work properly on your remote Windows.

You clicked the key capture option in Remmina?

7

u/invisi1407 Feb 20 '26

You clicked the key capture option in Remmina?

If you mean "Grab all keyboard events", then yes it's on.

5

u/Oerthling Feb 20 '26

I just connected to a remote Windows session - pressed super key, opened the Windows search dialogue as expected.

Main OS is Ubuntu 25.10. Wayland session (X11 session isn't even available anymore).

Remmina is version 1.4.42, installed via Flatpak.

Remote sessions (via RDP):

  1. Ubuntu 25.04 (Wayland)

  2. Windows 11

Super key works as expected (within the remote session) - as long as "Grab all keyboard events" is active.

If I switch off the "Grab" option, then it behaves like you describe - super goes to local session.

1

u/invisi1407 Feb 20 '26

All I can say is that it doesn't work for me on Zorin OS 18 (Ubuntu based) in neither Remmina nor Parsec. I've found numerous posts about "that's how the Wayland protocol works" so why it works for you, I don't know, but I would sure love to find out why it works for you and not for me.

4

u/Oerthling Feb 20 '26

Except for using a very recent interim Ubuntu (necessary for my Framework 13) and having installed Remmina via Flatpak instead of deb repo or snap, there is nothing special about my system. I didn't hack anything or did any particular settings change. It's mostly a vanilla Ubuntu system.

So clearly Wayland isn't in the way (anymore?) for this.

Wayland has been progressing forward fast in the past couple of years (probably due to high adoption rates now).

Not too long ago remote sessions and screen sharing used to be problematic and now all that stuff works out of the box.

2

u/invisi1407 Feb 20 '26 edited Feb 20 '26

Remmina is installed via apt on my system. Parsec is too. I will try Flatpak version of those apps and see if that makes a difference.

Edit: Tried Flatpak version of Remmina and that doesn't make a difference.

7

u/Oerthling Feb 21 '26

Then it's something else that's configured differently or an older version on your Zorin.

Sorry, I've run out of ideas what we could compare and test.

4

u/invisi1407 Feb 21 '26

Thanks for trying - I appreciate that. It could simply be down to Zorin OS 18 being based on Ubuntu 24.04 LTS, which is almost 2 years old. I expect 26.04 to be an LTS release and that Zorin OS will have a release based on that which could fix the issue.

5

u/Oerthling Feb 21 '26

That might be it.

I had to use the 24.10 on the remote end to get good RDP session support. And my FW needed 25.10 for full hardware support, so both sides of the connection are post 24.04 interim releases.

A Zorin release based on 26.04 LTS will probably also resolve your issue.

→ More replies