https://bugzilla.novell.com/show_bug.cgi?id=400520
User nice@titanic.nyme.hu added comment
https://bugzilla.novell.com/show_bug.cgi?id=400520#c14
--- Comment #14 from Tamás Németh
My experience is that when using the same keyboard layout on Xvnc and on the Xserver on the local machine (set it with setxkbmap) you don't run into such issues. But this is with Linux on both sides.
OK I adjusted the keyboard layouts on my KDE3 system by setxkbmap, but the remote session remained unaware of caps lock. (I use openSUSE 11.1) I suspect that it's not even a bug in Xvnc, but in the display managers (kdm/gdm) and desktop environments in some way, because the keyboard layout behaves differently before login: -With kdm, the initial screen (running kdm) handles the keyboard layout almost correctly The only problem is that after pressing any accentuated character, that accentuated character will be the only working accentuated character. All the other accentuated characters become disfunctional. -With gdm the accentuated characters work without problems. -With kdm, caps lock changes between upper/lowercase letters, but kdm does not give any warning popup message about the state of caps lock. -gdm cat detect the state of caps lock, so it send warning messages, but caps lock cannot make letters upper/lowercase. In addition to this, I realized, that KDE keyboard layout management cannot be used to do the workaround by setxkbmap. Maybe it calls setxkbmap with wrong options. How can I extract the keyboard layout informations (injected by setxkbmap) from the running X server? BTW, everything worked fine in openSUSE 10.3. Does it use xf4vnc like openSUSE 11.0 ans 11.1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.