error starting the GNOME Settings Daemon

[lasombra]

After updating the system today 17.09.2007 my gutsy tribe 5 (Kernel has a problem to start the gnome-settings-daemon with the error above. Starting manually from the shell ends up with the following error:
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 2218 error_code 2 request_code 147 minor_code 35)

[Richard Hamnett (richard-hamnett)]

Confirmed same problem with update today.

Have Intel I915 graphics card with -intel driver not -i810

rick@rick-laptop:~$ 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 1068 error_code 2 request_code 146 minor_code 35)
<snip>
[1190048421,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application

[wouter bolsterlee (wbolster)]

This has nothing to do with Gnome Specimen. No idea why this bug was filed for this project instead of Gnome control center.

[lasombra (lasombra)]

When I start via sudo, I receive the message, that the deamon could not connect to the dbus -> I've verified, that dbus is running

 sudo gnome-settings-daemon

** (gnome-settings-daemon:6509): WARNING **: Unable to connect to dbus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(gnome-settings-daemon:6509): GnomeKbdIndicator-WARNING **: Unable to connect to dbus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(gnome-settings-daemon:6509): GnomeKbdIndicator-WARNING **: Not connected to dbus, will not register the object
Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
                  Ignoring extra symbols
Warning: No symbols defined for <SYRQ> (keycode 92)
Warning: No symbols defined for <II65> (keycode 101)
Warning: No symbols defined for <BRK> (keycode 114)
Warning: No symbols defined for <FK13> (keycode 118)
Warning: No symbols defined for <FK14> (keycode 119)
Warning: No symbols defined for <FK15> (keycode 120)
Warning: No symbols defined for <FK16> (keycode 121)
Warning: No symbols defined for <FK17> (keycode 122)
Warning: No symbols defined for <KPDC> (keycode 123)
Warning: No symbols defined for <XFER> (keycode 129)
Warning: No symbols defined for <I02> (keycode 130)
Warning: No symbols defined for <NFER> (keycode 131)
Warning: No symbols defined for <I04> (keycode 132)
Warning: No symbols defined for <AE13> (keycode 133)
Warning: No symbols defined for <I06> (keycode 134)
Warning: No symbols defined for <I07> (keycode 135)
Warning: No symbols defined for <I08> (keycode 136)
Warning: No symbols defined for <I09> (keycode 137)
Warning: No symbols defined for <I0A> (keycode 138)
Warning: No symbols defined for <I0B> (keycode 139)
Warning: No symbols defined for <I0C> (keycode 140)
Warning: No symbols defined for <I0D> (keycode 141)
Warning: No symbols defined for <I0E> (keycode 142)
Warning: No symbols defined for <I0F> (keycode 143)
Warning: No symbols defined for <I10> (keycode 144)
Warning: No symbols defined for <I11> (keycode 145)
Warning: No symbols defined for <I12> (keycode 146)
Warning: No symbols defined for <I13> (keycode 147)
Warning: No symbols defined for <I14> (keycode 148)
Warning: No symbols defined for <I15> (keycode 149)
Warning: No symbols defined for <I16> (keycode 150)
Warning: No symbols defined for <I17> (keycode 151)
Warning: No symbols defined for <I18> (keycode 152)
Warning: No symbols defined for <I19> (keycode 153)
Warning: No symbols defined for <I1A> (keycode 154)
Warning: No symbols defined for <I1B> (keycode 155)
Warning: No sy...

[Gavin Graham (gavingraham)]

I am experiencing this too with Gutsy Tribe-5+updates. Trying to manually start the daemon returns the following:

** (gnome-settings-daemon:7557): WARNING **: The system configuration changed - but we remain silent

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 1439 error_code 2 request_code 147 minor_code 35)
  (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.)
[1190060238,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationgavin@gavin

[Richard Hamnett (richard-hamnett)]

Seems to have been remedied in todays updates Tuesday 18th Sept @ 3pm GMT

[Gavin Graham (gavingraham)]

I too can confirm that it seems to be fixed. Hasn't happened once since that last update I ran today and I have rebooted several (maybe 6) times.

[Pedro Villavicencio (pedro)]

Marking it as fixed then according to the comments, feel free to re open it if you experience the same problem again.

[Chris J (chriscf)]

Re-opening. This was still occurring after the the various fixes were supposedly released, and is still occurring as of 2.20.0-0ubuntu3.

[Ian B (ectogon)]

Confirming. I have this problem after upgrading from Feisty Fawn to Gutsy Beta and using version 2.20.0-0ubuntu4

[Rodrigo Virote Kassick (kassick)]

As of 2.20.0-0ubuntu5 , gnome-settings-daemon works ***if and only if*** it's display is a Xgl one.

When I first upgraded to gutsy, I had Xgl enabled and settings-daemon was working. Since Xgl does not behave well in my notebook, i've disabled it, and since then, settings-daemon would crash with the above message.

Executing Xgl :1 and gnome-settings-daemon with DISPLAY=:1 works. I've tested it with a fake user i've just created: settings daemon runs ok as long as I don't disable Xgl.

[Andrew Conkling (andrewski)]

I think I'm experiencing this periodically, but for reference also see bug #84876.

[KoZo (zoot-allures)]

I also get this message randomly...
For info, I made a clean install of Gutsy (Ubuntu Studio) twice.

[OPenango (openango-gmail)]

I am running Ubuntu 8.04, and recently I reconfigured my network connection to run ethernet, in addition to WiFi.
Now when I log in I get the GNOME warning (after ages waiting to load up after sign in)
There was an error starting the GNOME Settings Daemon
Some things, such as themes, sounds, or background settings may not work correctly.

Well - I ran sudi gnome-settings-daemon and got the following response
** ERROR ** You can run one xsettings manager at a time: exiting

Aborting...
Aborted

Not sure why there are multiple xsettings managers - how do I fix?

If nothing else - I will revert to Wifi, and remove ethernet/DHCP connection

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in gnome-control-center.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!