After a upgrade to control-center-2.12.2 or control-center-2.12.2-r1 Gnome gives a error after startup. Downgrading to 2.12.1 solves it The error message: Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: Gentoo (The X.Org Foundation 6.8.2, revision r6-0.1.13) 60802000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd As asked here are the results: xprop -root | grep XKB: _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "", "" _XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "", "" gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [us_intl] model = overrideSettings = false options = [grp grp:alts_toggle] Reproducible: Always Steps to Reproduce: 1. Upgrade to 2.12.2(-r1) 2. Logout 3. Login Actual Results: An error is displayed () Expected Results: Flawless login Portage 2.0.53 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r3, 2.6.14-gentoo-r4 x86_64) ================================================================= System uname: 2.6.14-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.0_pre11 dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.15 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-mtune=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-mtune=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_US.UTF-8" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X a52 aac accesibility accessibility acpi alsa audiofile avi berkdb bitmap-fonts bzip2 cairo cdparanoia cdr crypt cups curl daap dbus dpms dv dvd dvdr dvdread eds emboss emul-linux-x86 encode esd evo exif expat fam ffmpeg foomaticdb fortran gb gcj gdbm gif glitz glut gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile hal howl idn ieee1394 imagemagick imap imlib ipv6 java javascript joystick jpeg lcms ldap lua lzw lzw-tiff mad mime mng mozilla mp3 mpeg ncurses nls nptl nsplugin ogg openal opengl pam pcmcia pcre pdflib perl png python quicktime readline recode samba scanner sdl sndfile sockets sox speex spell sqlite ssl svg tcpd theora threads tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales v4l vcd vorbis wifi wmf wxwindows xinerama xml xml2 xosd xpm xrandr xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
I confirm this bug and it is severe - it renders the keyboard completely unusable. This ebuild should be hardmasked or something.
I am on amd64 as well btw.
Same here on x86. If I press "Reset to Defaults" button then it doesn't give me this error anymore. However if I add another layout, upon log in it will show me the same error. The result of xprop -root | grep XKB - after I reset to default _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "", "" _XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "", "" - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd also after layouts = [] model = overrideSettings = false options = []
It's a known bug. Look here : http://bugzilla.gnome.org/show_bug.cgi?id=322955 A patch is commited in libxklavier CVS HEAD. A new release will be released asap.
backported patch from freedesktop cvs, its in cvs now, 2.0-r1. Thanks to Chainsaw for poking me on this one :)
*** Bug 115169 has been marked as a duplicate of this bug. ***
Recently (Jan 3rd) I've upgraded to gnome-2.12 and after that I've encountered the same problem with xklavier-2.0. The problematic xklavier-2.0 is marked stable (!), so all people upgrading their gnome and using non-default keyboard layouts will have the same problems too. So I think that xklavier-2.0-r1 should be marked stable ASAP. (it's been three weeks already since allanonjl commited it to cvs) Thanks in advance.
I have xklavier 2.0-r1 and am receiving this error. However I am also using the Gnome experimental builds from breakmygentoo. Is it possible this is caused by the latest Gnome? Or is it klavier
I have xklavier 2.0-r1 and am receiving this error. However I am also using the Gnome experimental builds from breakmygentoo. Is it possible this is caused by the latest Gnome? Or is it klaviers fault?
(In reply to comment #8) > I have xklavier 2.0-r1 and am receiving this error. However I am also using > the Gnome experimental builds from breakmygentoo. Is it possible this is > caused by the latest Gnome? Or is it klavier
(In reply to comment #8) > I have xklavier 2.0-r1 and am receiving this error. However I am also using > the Gnome experimental builds from breakmygentoo. Is it possible this is > caused by the latest Gnome? Or is it klaviers fault? > I'm not an expert, but after I got the error I did the following: * downgraded to xorg-x11-6.8.2-r4 * emerged libxklavier-2.0-r1 That did the trick for me. Maybe I should upgrade to xorg-x11-6.8.2-r6 and see if the problem shows again?
It seems it was the same bug as reported in another bug, which I can
It seems it was the same bug as reported in another bug, which I cant find at the moment -- but the fix is: ln -s /usr/share/X11/xkb /usr/lib/X11/xkb
