-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Page_Up, Page_Down translated to \, Menu #4396
Comments
This is unrelated and fixed in 65eea92 - thanks for reporting it.
Looks correct to me. |
Yes, US layout (the norm here in New Zealand). |
I believe that c57e4d4 fixes the problem and will be backported to older branches. Hopefully it doesn't break any other platform.. |
Thanks, that indeed fixes it for me. |
This reverts commit 0a3334f. Which causes too many new problems with keyboard mapping.
@donaldsycamore is that a Wayland session by any chance? |
I think I know what happened here:
The commit above is a better fix and only uses the client keycode for X11 clients, other clients fall through to xpra/xpra/x11/server/keyboard_config.py Lines 477 to 478 in ce124c6
@donaldsycamore please confirm that fb72d90 also works for you. |
let the find_matching_keycode fall through use the keycode_translation for non X11 clients, as this may require using a different group
Not heard back. |
Describe the bug
On Debian Bookworm (latest stable), with Xpra installed via Xpra-provided debian packages, with GNOME 3 & Wayland, in Seamless mode, and US keymap, Page_Up on the client is translated to the "" key, and Page_Down is translated to Menu.
xpra start --start=xfce4-terminal
xpra gui
-> connect -> SSH, username & hostname -> copnnectxpra toolbox
-> Keyboard running in a normal login session correctly showsPage_Up
andPage_Down
. xpra toolbox -> Keyboard running on the Xpra server showsKP_Divide
andMenu
System Information (please complete the following information):
Additional context
Keyboard debugging on the client shows logs like:
PageUp:
PageDown:
This issue also occurs when I use a client running on PostmarketOS (Alpine Linux) to connect to this same session.
The text was updated successfully, but these errors were encountered: