-
-
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
no dead keys with german keyboard from windows client to linux server #4449
Comments
Keyboard debug log output
|
Have you tried switching input methods with |
TILs, the key events seen:
I would need to look at the server log to see what events are being produced there. |
Here is the server log...
|
Here are my test results with different
|
TBH, I have no idea which input method should be the default! ( Are you problems fully resolved? |
Using However the keys are working as dead keys now, which is rather cumbersome when coding. (I have to press them twice to obtain the corresponding character.) On my linux systems I'm using the nodeadkeys keyboard variant to avoid that. But in this case I am connecting from a windows client (which doesn't have a nodeadkeys variant) and I was trying to set up an xpra session to a linux server using Do you have a hint how to configure |
Ah, gotcha. I never use these kinds of layouts myself, so I am a bit lost. One way forward would be to connect from a working Linux X11 client, then post the server log so we can see what "correct" settings are being used to get The fact that nothing works at all for you with Another idea, the latest commits also allow you to change the keyboard model: #4445 (comment) |
First, I assume that you have mixed up your client and server in the bug description?
This should be the same as the default ( Lines 162 to 168 in a181b0c
The ibus documentation is seriously lacking. According to ibus/ibus#1878 : This is an expected warning but not an error. The warning happens whether your pinyin has a problem or not.
Good, but not very user friendly!
Xpra does not set anything in ibus, it only starts it.
IIRC, it never worked properly.
Or maybe this is all superfluous and #4463 fixes it? |
Oops! Sorry. I updated the info in the original post.
Unfortunately not. I just tried xpra-6.3-10.r37076 on the (Rocky Linux 9) server side. However I could not reproduce this issue:
|
I found some easy examples using gi Use |
this prevents the hello packet from growing too large
Cool!
Hmm - strange. |
Maybe a component is missing, perhaps the There are some newer builds in the beta area, maybe that will help? d690dd9 also adds a |
When connecting from a Windows 10 client to a linux server, dead keys (accent keys that need a subsequent key) do not work. (E.g. ^ followed by SPACE yields just the SPACE). The keys
^
,`
and´
produce no output.--no-keyboard-sync
doesn't make a difference--keyboard-layout=de --keyboard-variant=nodeadkeys
.dead-circumflex
,dead-grave
anddead-acute
(see below).System Information (please complete the following information):
Additional context
On the Windows client
.\Keymap_info.exe
.\Keymap_info.exe
On the Linux server
$ setxkbmap -print
$ setxkbmap -query
$ xmodmap -pke
$ xmodmap -pm
xev
doesn't show an event when pressing the corresponding keys.The text was updated successfully, but these errors were encountered: