-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
PgUp and PgDn get mapped to different keys on the server #4292
Comments
Are you sure this is correct? Why do you need to specify Have you tried |
Sorry, fixed it.
I tried it with both settings for both of the keyboard flags. This was my latest incantation.
Yes, I did after I filed this issue. Same symptoms. |
No, this looks like a kernel version, not an OS version: |
Debian Bookworm on both client and server. |
Symptoms persist without any of Symptoms are worse with ` |
Please post the client output, which contains keyboard detection information. |
I finally had a chance to re-install the client-machine xpra (due to external constraints, it's not quite a standard install), and now everything seems to be working---or at least, I'm not seeing this problem any more. |
Describe the bug
The
PgUp
key gets interpreted as/
, and thePgDn
key gets interpreted asMenu
on the Xpra server.To Reproduce
Steps to reproduce the behavior:
xpra start --ssh="ssh -x -C " --keyboard-sync=no --opengl=no --keyboard-layout=us --title="@client-machine@: @title@" ssh://${USER}@${REMOTE}/100 --start=xfce4-terminal
PgUp
andPgDown
on an Xpra window. The former becomes a slash/
, the latter becomes aMenu
-key press. They work fine on my local machine.System Information (please complete the following information):
Additional context
I have a standard 104-key US keyboard, and I don't specify any keyboard mappings.
It seems that the
xpra
server interprets the samekeycode
as the my client machine, but translates it to a differentkeysym
. Compare the output ofxev
on both machines:local machine
xpra server
The text was updated successfully, but these errors were encountered: