after upgrading to gnome-2.18 logging into gnome produces a scrambled keyboard mappings. after some research i've copied a work around using xmodmap to save the correct keyboard mappings (produced via 'xmodmap -prv > /tmp/xmodmap.map') by logging in without gnome (i used twm, others used kde). either way resetting the keymap via a script on login corrects this issue but it appears to be a standing one. n.b: apparently there was a related issue with vino that has been resoloved in vino but looking at that bug report i'm i'm guessing this was a hack and that gnome-keyboard-properties is, in fact pulling incorrect keyboard mappings from the server itself my configuration is running tightvnc servers via the xdm and via xinetd connecting back via XDCMP. both servers exhibit the same issue. i have also configured a standard X server on the machine and tested that. whilst that operates correctly it displays a message stating that the X keyboard and the gnome keyboard settings do not match and requesting which to select (either produces correct results) i have rebuilt gnome in it's entirety using '--emptytree' but to no avail. Reproducible: Always Steps to Reproduce: 1.install tightvnc 2.run gnome-2.18 in tightvnc session Actual Results: keyboard mapping mangled Expected Results: keypress to produce corresponding symbol on screen this can also be tested by booting into twm or other window manager and running the gnome-keyboard-properties manually.
please paste `emerge --info` here as well. @armin ... none of us really use VNC, what's your take on this?
(In reply to comment #1) > please paste `emerge --info` here as well. > > @armin ... none of us really use VNC, what's your take on this? > Portage 2.1.3.7 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.19-gentoo-r5-louvre i686) ================================================================= System uname: 2.6.19-gentoo-r5-louvre i686 Pentium III (Coppermine) Gentoo Base System release 1.12.10 Timestamp of tree: Fri, 31 Aug 2007 08:00:04 +0000 app-shells/bash: 3.2_p17-r1 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4, 2.5.1-r2 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.10-r4 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18 sys-devel/gcc-config: 1.4.0-r2 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.22-r2 ACCEPT_KEYWORDS="x86 ~x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=pentium3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://ftp.heanet.ie/pub/gentoo/ ftp://212.219.56.133/sites/www.ibiblio.org/gentoo/ http://212.219.56.138/sites/www.ibiblio.org/gentoo/ http://212.219.56.135/sites/www.ibiblio.org/gentoo/ http://212.219.56.134/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acl alsa berkdb bitmap-fonts cli cracklib crypt cups dbus dri flac fortran gdbm gpm gtk hal iconv ipv6 isdnlog java mad midi mono mpeg mudflap ncurses nls nptl nptlonly nsplugin ogg openmp pam pcre perl pppd python readline reflection session spl ssl tcpd theora truetype-fonts type1-fonts unicode vorbis x86 xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" FOO2ZJS_DEVICES="hp2600n" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mach64 mga neomagic nsc nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
I'd say this is more for upstream...
(In reply to comment #3) > I'd say this is more for upstream... sorry, could i ask what this means? also, for the record, i have a fairly workable workaround by writing a short script to load the correct keymap (captured as per original message) and adding a launcher for this script into /usr/share/gnome/autostart. this, obviously, has severe limitations as a generic workaround
(In reply to comment #4) > (In reply to comment #3) > > I'd say this is more for upstream... > > sorry, could i ask what this means? > > also, for the record, i have a fairly workable workaround by writing a short > script to load the correct keymap (captured as per original message) and adding > a launcher for this script into /usr/share/gnome/autostart. this, obviously, > has severe limitations as a generic workaround > I mean this bug should go to the developers of tightvnc.
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > I'd say this is more for upstream... > > > > sorry, could i ask what this means? > > > > also, for the record, i have a fairly workable workaround by writing a short > > script to load the correct keymap (captured as per original message) and adding > > a launcher for this script into /usr/share/gnome/autostart. this, obviously, > > has severe limitations as a generic workaround > > > > I mean this bug should go to the developers of tightvnc. > OK. thought the fact that it's only an issue with gnome-keyboard-properties that gnome upstream (if i have terminology correct) would be a better destination but perhaps there'll be better response from tightvnc devs around the issue. should i post this to them via their own procedures or do gentoo package people generally manage this? apologies for my ignorance in these matters
I finally found this today, 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. Unfortunately, I have no idea where that falls in with tightvnc, you're on your own to figure it out :) Thanks
I disabled the keyboard and a11y-keyboard plugins in the configuration editor, then restarted my VNC session. This fixed the issue for me. There is a discussion here: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/320393 https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/199245 And several other places. Check Applications --> System Tools --> Configuration Editor And look for the following keys: /apps/gnome-settings-daemon/plugins/keyboard /apps/gnome-settings-daemon/plugins/a11y-keyboard Uncheck the 'active' flag in both of these entries.
Are you still suffering this with 2.26? (it should include https://bugzilla.gnome.org/show_bug.cgi?id=537592 fix)
(In reply to comment #9) > Are you still suffering this with 2.26? (it should include > https://bugzilla.gnome.org/show_bug.cgi?id=537592 fix) > Closing then for now, but feel free to reopen if still valid
