-
-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't switch keyboard layout on xpra 6.2.x #4445
Comments
I found the way to switch by console commands with preparation. But still I can't switch by keys combination.
So does it mean that issue with X session settings? |
AFAICT, that's a limitation of Wayland clients. You could run the xpra client with the X11 backend to see if that helps: |
|
You can run the client with |
I did it. And as far as I can see all keys detected properly. |
Ha I just set up rshift_tggle and it kinda works but only when I hold right shift. Looks like it behaves not as toggle but as switch but some progress. |
It's not the keys that I expected to see. I was hoping there would be a
I don't see how the server would have configured x11 layout switching unless you configured that yourself manually.
With X11 clients (and depending on the exact configuration), the layout change can be detected as an X11 event, it is then forwarded to the server which then mirrors it. |
I'm working on dirty hack 😀: installed
Looks like xpra override keyboard settings that were set up by setxkbmap |
Yes, the first thing xpra does when you connect is to setup the keyboard. |
A better way would be to use |
Is this for server ? I tried it as well, didn't work.
Hmmm I thought that here we can set only options like we do in for |
Is there a way to emulate this event? |
The client can supply it: Lines 65 to 101 in a98ab0d
The system tray keyboard layout menu kinda does. |
Looks interesting. I'll try to understand how it works.
How to get it in seamless mode? |
This works: |
FWIW, with my X11 client, the server does this:
Connecting from a Wayland client, the keyboard detection is much more limited and shows:
As of commit 0a43ed8, I can now also change the default layout on the server: XKB_DEFAULT_MODEL=pc105 xpra start --start=xterm And then I get:
And with 89263b3, you can now also do the same from the client:
Does that help? |
Exactly!
Glad to hear about any progress. Actually in KDE settings I select pc105 and it works fine but when I set keyboard model by setxkbmap it matches pc104 due Russian layout. So pc105 as default I guess is good but if it's possible to override by some extra key during CLI or/and GUI it would be great! |
I don't understand - you also said that your client OS is
I am worried that this will cause regressions with the more unusual keyboard layouts, so I am going to leave it as it is for now.
Could be done, but I don't have the time for it. |
Sorry for confusing you. I have a server with Kubuntu 24.10. When I attach by NoMachine as a remote desktop it also does not recognize my client keyboard switching (Caps lock), but another combination (ctrl+space) does. Also I set keyboard as PC105 and other setting by KDE Plasma settings app and it works good. But when I connect by XPRA in seamless mode I have to use
Got it. Sounds reasonable.
Sounds like merge requests are welcome, right? 😉 |
Definitely, it should be relatively straightforward to add a sub-menu here: xpra/xpra/client/gtk3/tray_menu.py Lines 1164 to 1173 in ea92b9c
And populate the list of models from a hard-coded list. |
FYI: see also #4449 (comment) |
@totaam cool! It works! Thank you both @totaam and @kpushkaryov . |
Can't switch keyboard layout on xpra 6.2.x by Ctrl+Space or other combinations.
Steps to reproduce the behavior:
xpra start :12 --start=kate
xpra attach ssh://name@ip/12
Kubuntu 24.10 (X server arm64 Oracle Cloud VM)
Kubuntu 24.10 (Wayland)
v6.2.1-r0
(There is no 6.2.2 for arm64)v6.2.2-r0
(amd64)Additional info
xpra toolbox
catches Ctrl and Space--no-keyboard-sync
tried
setxkbmap -layout 'us,ru' -model pc105 -option 'grp:ctrl_space_toggle,grp_led:scroll'
(with no luck)xmodmap -pm
xkbprint -label name $DISPLAY
-d keyboard
Pressed: 'a','b','c','Ctrl','Space','Ctrl+Space','Caps Lock'server-d_keyboard.log
client-d_keyboard.log
The text was updated successfully, but these errors were encountered: