After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 322955 - XKB settings broken in 2.12.2
XKB settings broken in 2.12.2
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 323462 (view as bug list)
Depends on:
Reported: 2005-12-01 19:32 UTC by Arwed v. Merkatz
Modified: 2005-12-07 15:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Arwed v. Merkatz 2005-12-01 19:32:55 UTC
The setup of the XKB settings at startup of the session is broken in
control-center 2.12.2. It displays this error:
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:
The X.Org Foundation

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

arwed@Otherland:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc104", "us", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc104", "us", "", ""

arwed@Otherland:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [us,de	deadgraveacute]
 model = scorpius
 overrideSettings = false
 options = [ctrl	ctrl:nocaps,grp	grp:alt_shift_toggle,grp_led	grp_led:scroll]


The exact same configuration works fine in control-center 2.12.1, it also works
fine if I go to the keyboard properties afterwards and change some setting.
Comment 1 Fryderyk Dziarmagowski 2005-12-01 22:53:46 UTC
Confirmed. This is serious regresion in 2.12.2, I'm not able to use keyboard
layout other then default.
p.s. this sucks, I can't change status to confirmed :\
Comment 2 Rodrigo Moya 2005-12-02 01:30:44 UTC
an update of libxklavier is also needed for this bug to disappear. Not sure if
there was a release of that for GNOME 2.12.2
Comment 3 Sergey V. Udaltsov 2005-12-02 07:59:10 UTC
There was no release of libxklavier for some while.
Comment 4 Fryderyk Dziarmagowski 2005-12-02 16:43:37 UTC
If it depends on unreleased stuff, so why it is released at all? To be marketed
primarily as "Quality"? ;>

% grep klavier
PKG_CHECK_MODULES(LIBXKLAVIER, libxklavier >= 1.14,,

Shouldn't it be 2.0 at least (because of ugly double free with glibc >= 2.3.5 in
old versions) ?
Comment 5 Fryderyk Dziarmagowski 2005-12-02 21:39:04 UTC
ok, I've just updated libxklavier to cvs HEAD version and bug described above is
still present. Smells like #320157 screwed up things.
Comment 6 Sebastien Bacher 2005-12-03 12:54:44 UTC
Ups I was supposed to forward the fix I made for Ubuntu (where is the place to
send libxklavier patches?):

--- libxklavier/xklavier_config_xkb.c
+++ libxklavier/xklavier_config_xkb.c
@@ -223,7 +223,7 @@
           exit( 1 );
           /* parent */
-          pid = wait( &status );
+         pid = waitpid( cpid, &status, 0 );
           XklDebug( 150, "Return status of %d (well, started %d): %d\n", pid,
cpid, status );
           memset( (char *)&result, 0, sizeof(result) );
           result.xkb = XkbAllocKeyboard();

Closing as NOTGNOME. Sergey could you apply the change to libxklavier? The issue
is that the current code wait for any process and unblock on the wrong one. The
patch makes it wait on the correct one.
Comment 7 Sergey V. Udaltsov 2005-12-03 13:26:00 UTC
I will commit it ASAP. Just one question, out of curiosity - which process
actually made 'wait' return? And another - is 'waitpid' as crossplatform as wait?
Comment 8 Sergey V. Udaltsov 2005-12-03 13:49:07 UTC
committed. Will make the release asap.
Comment 9 Sebastien Bacher 2005-12-04 15:23:15 UTC
I've not tried to track what process does that, but that's due to the
gnome-settings-daemon changes to not block before spawning different process on
startup. waitpid is posix as wait is
Comment 10 Sebastien Bacher 2005-12-07 15:12:01 UTC
*** Bug 323462 has been marked as a duplicate of this bug. ***