After updated my Gentoo (did "emerge -DNuv world"), and forced to be unable to use RealVnc's vncserver, I started using tightvnc's vncserver. Then my gnome-session connection was messed up with wrong keymap. My solution: un-emerge tightvnc, then emerge tigervnc and start the vncserver as usual, everthing works fine. Reproducible: Always Steps to Reproduce: 1. emerge tightvnc -- to install vncserver 2. configure .vnc/xstartrc with gnome-session, and the start vncserver 3. using RealVnc viewer from a Windows PC to login vncserver. Then keymap is wrong. Actual Results: When press ENTER key, it produces a SPACE key. Expected Results: When press ENTER keay, it should produce ENTER.
*** Bug 303379 has been marked as a duplicate of this bug. ***
Chances are that gnome hates not having xkb extension. Did you check xorg log ?
(In reply to comment #2) > Chances are that gnome hates not having xkb extension. > > Did you check xorg log ? > I'd like to. Please tell me how to check xorg log. BTW, my solution of using tigervnc still has some weired key mapping, so I guess it's not a good solution. Please let me know how I should fix it.
Hi, I got exactly the same problem. I found a workaround in bug #190865#c7 : > try setting XKL_XMODMAP_DISABLE=1 in your environment somewhere > before running gnome-session. In theory, that should tell gnome to be > very stupid about keyboard handling, and it should prevent it > from messing up your keymaps. This fix the problem for me.
seems a broken configuration led to the problem and the solution was found. Can we close this bug?
