gnome-settings-daemon exits with stupid error

Gullible Jones · 2005-12-30 21:45:32

[proteus@localhost ~]$ 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 342 error_code 2 request_code 116 minor_code 0)
  (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.)
[1135978818,000,xklavier.c:XklStartListen/]     The backend does not require manual layout management - but it is provided by the application
[1]+  Exit 1                  /opt/gnome/libexec/gnome-settings-daemon
[proteus@localhost ~]$ /opt/gnome/libexec/gnome-settings-daemon
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 342 error_code 2 request_code 116 minor_code 0)
  (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.)
[1135978834,000,xklavier.c:XklStartListen/]     The backend does not require manual layout management - but it is provided by the application[proteus@localhost ~]$

This cropped up out of nowhere after I switched from the "mouse" driver to "evdev". I have absolutely no idea what could cause it. One thing is certain, though - this error *always* occurs when I use evdev, and *never* occurs when using a different driver.

phrakture · 2005-12-30 22:01:31

what is this?

[1135978818,000,xklavier.c:XklStartListen/]     The backend does not require manual layout management - but it is provided by the application

After some googlage:

libxklavier - utility library to make XKB stuff easier

'BadValue' errors are one of the awesomely-generic X errors that it spits out - hell, the wmi errorhandler actually ignores alot of BadValue and BadWindow errors because they happen alot and there's no way to really track it down.

Fun times - have to attack it from another angle.

Looks like libxklavier uses "XKL_DEBUG" for verbosity... try "export XKL_DEBUG=150" before starting X.

phrakture · 2005-12-30 22:06:06

Second thought - evdev can also handle keyboards... they "layout management" error refers to keyboard layouts... so obviously xklavier and evdev are clashing on keyboard handling... don't ask me how to shut these off, I don't know

Gullible Jones · 2005-12-30 22:36:36

Bloody hell.

(This is really weird, evdev doesn't do this with my old mouse... Only with my new A4Tech trackball.)

phrakture · 2005-12-30 23:15:33

Hang on - full nack to what I said earlier... the libxklavier stuff doesn't fail. It just spits out that message and continues on it's merry way. So, most likely it's not what I said before.
:oops:

evdev really doesn't do much... it's like a 4K C file.

Try debugging X in gdb (should be full of hilarity) and see if you can dump and symbols from a backtrace.

Gullible Jones · 2005-12-30 23:38:43

Ack, my bad, same problem with my old mouse. Sh*t.

Anyway, how would I go about doing a traceback? Sorry, I'm not very familiar with gdb.

JGC · 2005-12-31 00:29:11

It's an issue with evdev and libxklavier. evdev doesn't support XKB mapping as the old keyboard and mousedrivers used to do. When I enable evdev for my mouse, I get the same error as you have and my gnome looks like garbage.

Gullible Jones · 2006-01-01 15:08:43

Argh! Still happens with the new libxklavier! :evil:

Gullible Jones · 2006-01-02 16:26:44

Alright guys, filed a bug. JGC, would you mind confirming this?

JGC · 2006-01-02 23:16:06

Looks like some wrong logic exists in the gnome-settings-daemon code:
http://bugzilla.gnome.org/show_bug.cgi?id=323724

Gullible Jones · 2006-01-02 23:25:53

Damn. The fix for this probably won't be out for a long time...

Arch Linux

#1 2005-12-30 21:45:32

gnome-settings-daemon exits with stupid error

#2 2005-12-30 22:01:31

Re: gnome-settings-daemon exits with stupid error

#3 2005-12-30 22:06:06

Re: gnome-settings-daemon exits with stupid error

#4 2005-12-30 22:36:36

Re: gnome-settings-daemon exits with stupid error

#5 2005-12-30 23:15:33

Re: gnome-settings-daemon exits with stupid error

#6 2005-12-30 23:38:43

Re: gnome-settings-daemon exits with stupid error

#7 2005-12-31 00:29:11

Re: gnome-settings-daemon exits with stupid error

#8 2006-01-01 15:08:43

Re: gnome-settings-daemon exits with stupid error

#9 2006-01-02 16:26:44

Re: gnome-settings-daemon exits with stupid error

#10 2006-01-02 23:16:06

Re: gnome-settings-daemon exits with stupid error

#11 2006-01-02 23:25:53

Re: gnome-settings-daemon exits with stupid error

Board footer