gnome-settings-d crashes after update of xkeyboard-config

Bug #26310 reported by D Oosterveld
8
Affects Status Importance Assigned to Milestone
control-center (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Problem with gnome-settings-daemon when upgrading xkeyboard-config from
0.6-5 to 0.6-5breezy1. gnome-settings-deamon crashes.

Running Ubuntu Breezy on a HP Laptop ze4400. No problems encountered until
update of xkeyboard-config. I have installed all the latests updates.

GNOME settings daemon exits with:

There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work correctly.
The Settings Daemon restarted too many times.
The last error message was:
Child process did not give an error message, unknown failure occurred
GNOME will still try to restart the Settings Daemon next time you log in.

In the terminal the gnome-settings-daemon outputs:

Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
                  Ignoring extra symbols
Warning: No symbols defined for <SYRQ> (keycode 92)
<... More warnings for symbols ...>
Warning: No symbols defined for <I7E> (keycode 254)
Warning: No symbols defined for <I7F> (keycode 255)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 807 error_code 2 request_code 147 minor_code 9)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[1133172382,000,xklavier.c:XklStartListen/] The backend does not require
manual layout management - but it is provided by the application

Problem is solved when the packages is downgraded from xkeyboard-config
0.6-5breezy1 to 0.6-5.

Output from gconftool-2:
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd

 layouts = [us intl]
 model = hpxt1000
 options = [grp grp:alts_toggle,eurosign eurosign:5,Compose key
compose:ralt,lv3 lv3:lwin_switch]
 overrideSettings = true

I noticed libxklavier crashes frequently if keyboard settings are changed and
the configuration does not reflect the updated xkeyboard-config.

Reproduce:

Reproduce this by probably using the same keyboard settings and updating back
and forth between xkeyboard-config 0.6-5 and 0.6-5breezy1

I have done this twice and both times the gnome-settings-daemon leaves me with
a default gnome desktop.

Revision history for this message
Daniel Stone (daniels) wrote :

for most people, the problem is exactly the reverse (see #15372). can't
reproduce here. odd. does it work in dapper?

Daniel Stone (daniels)
Changed in xkeyboard-config:
assignee: daniels → nobody
Revision history for this message
D Oosterveld (d-oosterveld) wrote :

I've moved to dapper-drake which included the new xkeyboard-config data. Gnome settings deamon crashed again but after reconfiguring the keyboard settings the problem is solved.

I think there was a problem with how I had my keyboard configured. I think this configuration pointed to some keyboard layout that didn't exist anymore after the update.

gnome-settings-deamon (libxklavier) shouldn't crash on misconfiguration. so I think it is still a bug and could disappoint some users with misconfigured keyboard layouts when they upgrade.

happy hunting ;)

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

As the xkeyboard-config part of the bug has been fixed, reassigning to gnome-control-center

Revision history for this message
Sebastien Bacher (seb128) wrote :

Does anybody still has the issue and could describe the config he uses getting it?

Changed in gnome-control-center:
assignee: nobody → desktop-bugs
Revision history for this message
Sebastien Bacher (seb128) wrote :

No reply, bug closed. Feel free to reopen if you still get the issue with dapper or edgy

Changed in control-center:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.