http://bugzilla.novell.com/show_bug.cgi?id=400520
User jrgn.keil@googlemail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=400520#c28
Jürgen Keil changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jrgn.keil@googlemail.com
--- Comment #28 from Jürgen Keil 2009-05-17 05:35:42 MDT ---
As far as I understand it, the root cause for this problem is
that there are two keyboard devices in Xvnc now, an id=0
"Virtual core keyboard" and an id=2 VNC XExtensionKeyboard.
Keycodes for the umlaut keys are dynamically added to
the id=2 XExtensionKeyboard, but the gui applications
use the keysym mapping table from the id=0
"Virtual core keyboard".
$ xinput list
"Virtual core keyboard" id=0 [XKeyboard]
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Virtual core pointer" id=1 [XPointer]
Num_buttons is 32
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is 0
Max_value is -1
Resolution is 0
Axis 1 :
Min_value is 0
Max_value is -1
Resolution is 0
"" id=2 [XExtensionKeyboard]
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"" id=3 [XExtensionPointer]
Num_buttons is 5
Num_axes is 2
Mode is Relative
Motion_buffer is 8
Axis 0 :
Min_value is 0
Max_value is -1
Resolution is 0
Axis 1 :
Min_value is 0
Max_value is -1
Resolution is 0
A possible fix is to change Xvnc file hw/vnc/kbdptr.c
function KbdAddEvent() to use "inputInfo.keyboard"
(= id0 core keyboard) instead of "kbdDevice"
(= id2 VNC keyboard). That way the new dynamically
added keycode/keysyms entries for the umlaut keys
are seen by X clients.
With such a fixed applied to the opensuse 11.1 Xvnc
server the umlaut keys start to work.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.