Unable to start the settings manager 'gnome-settings-daemon'.

Same problem on a Dell Inspiron 6000 after upgrade from feisty to gutsy beta. Also experiencing bug 126797, perhaps related.

tried running the daemon via the terminal, get the following:

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 1600 error_code 2 request_code 146 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.)
[1191375676,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationthom@dell:~

I am also experiencing bug 126797

Thanks for your comments. This does not appear to be a bug report as such. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. http://launchpad.net/support

Then let me know what I can do to make this a bug report. I've got a buggy laptop after upgrade that worked perfectly fine before upgrade. That's not a support issue, that's something going wrong with upgrade.

a bug report is something which has enough informations to be worked, not "it doesn't work after upgrade", having a way to trigger the bug or a backtrace of the crash would be useful informations, if you don't know how to get those maybe try the support tracker and somebody will guide you there then you can reopen the bugs with the informations

Related support issue:
https://answers.launchpad.net/ubuntu/+question/4499

Related bug:
bug 139368

Attempting a backtrace produces no information not already shown in the crash i posted earlier in this report.

Posted again here:

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 1600 error_code 2 request_code 146 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.)
[1191375676,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application

here's an strace if that helps

oops, strace with full output:

gnome-control-center-dbg package not available in gutsy, so I'm afraid that's the best I can do

Also being discussed here: http://ubuntuforums.org/showthread.php?t=553094&page=7

Okay, managed to get a backtrace.

http://wiki.ubuntu.com/DebuggingProgramCrash has instructions on how to install dbgsym packages, you might want to install gnome-control-center-dbgsym libglib2.0-0-dbgsym libgtk2.0-0-dbgsym

Reopening after adding strace and backtrace information. Happy to add more if needed.

I tried gnome-control-center-dbgsym -- didn't help.

also added all the available gnome -dbg packages, but read somewhere that you have to use one or the other?

Installed all three dbgsym packages as requested. Backtrace still looks the same though.

hmm, well not the same after all, there are some additional threads listed... attaching the latest

trying to add dbgsym for libbonoboui...

now i get this:

Breakpoint 2, gdk_x_error (display=0x808f100, error=0xbfa44568)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
614 /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c: No such file or directory.
        in /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c
(gdb) bt
#0 gdk_x_error (display=0x808f100, error=0xbfa44568)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
#1 0xb7199655 in bonobo_x_error_handler (display=0x808f100, error=0xbfa44568)
    at bonobo-ui-main.c:58
#2 0xb7f8bf50 in xkl_process_error () from /usr/lib/libxklavier.so.11
#3 0xb787ac4a in _XError () from /usr/lib/libX11.so.6
#4 0xb787c714 in _XReply () from /usr/lib/libX11.so.6
#5 0xb793084f in XChangeDeviceControl () from /usr/lib/libXi.so.6
#6 0x0805dc60 in ?? ()
#7 0x0808f100 in ?? ()
#8 0x080f5178 in ?? ()
#9 0x00000001 in ?? ()
#10 0xbfa446ec in ?? ()
#11 0x080f4130 in ?? ()
#12 0xbfa44708 in ?? ()
#13 0x00000000 in ?? ()

and after installing libxi6-dbgsym

Breakpoint 2, gdk_x_error (display=0x808f100, error=0xbfa44568)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
614 /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c: No such file or directory.
        in /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c
(gdb) bt
#0 gdk_x_error (display=0x808f100, error=0xbfa44568)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
#1 0xb7199655 in bonobo_x_error_handler (display=0x808f100, error=0xbfa44568)
    at bonobo-ui-main.c:58
#2 0xb7f8bf50 in xkl_process_error () from /usr/lib/libxklavier.so.11
#3 0xb787ac4a in _XError () from /usr/lib/libX11.so.6
#4 0xb787c714 in _XReply () from /usr/lib/libX11.so.6
#5 0xb793084f in XChangeDeviceControl () from /usr/lib/libXi.so.6
#6 0x0805dc60 in ?? ()
#7 0x0808f100 in ?? ()
#8 0x080f5178 in ?? ()
#9 0x00000001 in ?? ()
#10 0xbfa446ec in ?? ()
#11 0x080f4130 in ?? ()
#12 0xbfa44708 in ?? ()
#13 0x00000000 in ?? ()

grr, old content in clipboard -- here again:

#0 gdk_x_error (display=0x808f100, error=0xbfc63778)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
#1 0xb71a2655 in bonobo_x_error_handler (display=0x808f100, error=0xbfc63778)
    at bonobo-ui-main.c:58
#2 0xb7f94f50 in xkl_process_error () from /usr/lib/libxklavier.so.11
#3 0xb7883c4a in _XError () from /usr/lib/libX11.so.6
#4 0xb7885714 in _XReply () from /usr/lib/libX11.so.6
#5 0xb793984f in XChangeDeviceControl (dpy=0x808f100, dev=0x80f8660,
    control=1, d=0xbfc638fc) at ../../src/XChgDCtl.c:206
#6 0x0805dc60 in ?? ()
#7 0x0808f100 in ?? ()
#8 0x080f8660 in ?? ()
#9 0x00000001 in ?? ()
#10 0xbfc638fc in ?? ()
#11 0x080f4030 in ?? ()
#12 0xbfc63918 in ?? ()
#13 0x00000000 in ?? ()

and here with libX11-dbgsym installed. don't see any debug package for xklavier.

#0 gdk_x_error (display=0x808f100, error=0xbf9becd8)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
#1 0xb7117655 in bonobo_x_error_handler (display=0x808f100,
    error=0xbf9becd8) at bonobo-ui-main.c:58
#2 0xb7f09f50 in xkl_process_error () from /usr/lib/libxklavier.so.11
#3 0xb77f8c4a in _XError (dpy=0x808f100, rep=0xbf9bedd4)
    at ../../src/XlibInt.c:2907
#4 0xb77fa714 in _XReply (dpy=0x808f100, rep=0xbf9bedd4, extra=0,
    discard=1) at ../../src/XlibInt.c:1833
#5 0xb78ae84f in XChangeDeviceControl (dpy=0x808f100, dev=0x80f8660,
    control=1, d=0xbf9bee5c) at ../../src/XChgDCtl.c:206
#6 0x0805dc60 in ?? ()
#7 0x0808f100 in ?? ()
#8 0x080f8660 in ?? ()
#9 0x00000001 in ?? ()
#10 0xbf9bee5c in ?? ()
#11 0x080f4030 in ?? ()
#12 0xbf9bee78 in ?? ()
#13 0x00000000 in ?? ()

Since this looks like it might have something to do with the keyboard, might be worth mentioning that I'm using a German keyboard... will try changing the layout...

That didn't help. When I tried logging out and back in just now, all the panel applets crashed when loading.

Does typing "symbol-file /usr/lib/debug/usr/lib/gnome-control-center/gnome-settings-daemon" on the gdb prompt before getting the backtrace makes a difference?

Tried that, got this:

#0 gdk_x_error (display=0x808f100, error=0xbfcbcfd8)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
#1 0xb7122655 in bonobo_x_error_handler (display=0x808f100, error=0xbfcbcfd8)
    at bonobo-ui-main.c:58
#2 0xb7f14f50 in xkl_process_error () from /usr/lib/libxklavier.so.11
#3 0xb7803c4a in _XError (dpy=0x808f100, rep=0xbfcbd0d4)
    at ../../src/XlibInt.c:2907
#4 0xb7805714 in _XReply (dpy=0x808f100, rep=0xbfcbd0d4, extra=0, discard=1)
    at ../../src/XlibInt.c:1833
#5 0xb78b984f in XChangeDeviceControl (dpy=0x808f100, dev=0x810ab00,
    control=1, d=0xbfcbd15c) at ../../src/XChgDCtl.c:206
#6 0x0805dc60 in set_vert_scroll (state=<value optimized out>)
    at gnome-settings-mouse.c:372
#7 0x0805de65 in gnome_settings_module_mouse_start (module=0x80c0c40)
    at gnome-settings-mouse.c:612
#8 0x0805cd2d in gnome_settings_module_start (module=0x80c0c40)
    at gnome-settings-module.c:141
#9 0x08058923 in start_modules (daemon=<value optimized out>,
    runlevel=GNOME_SETTINGS_MODULE_RUNLEVEL_XSETTINGS)
    at gnome-settings-daemon.c:112
#10 0x08058983 in start_modules_idle_cb (user_data=0x80bed30)
    at gnome-settings-daemon.c:231
#11 0xb7654551 in g_idle_dispatch (source=0x80f4748, callback=0xbfcbcfd8,
    user_data=0x80bed30) at /build/buildd/glib2.0-2.14.1/glib/gmain.c:4132
#12 0xb765611c in IA__g_main_context_dispatch (context=0x809b1c0)
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c:2061
#13 0xb765955f in g_main_context_iterate (context=0x809b1c0, block=1,
    dispatch=1, self=0x8074470)
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c:2694
#14 0xb7659909 in IA__g_main_loop_run (loop=0x80c3cb8)
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c:2898
#15 0xb7b8d9e4 in IA__gtk_main ()
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkmain.c:1144
#16 0x08055bd4 in main (argc=0, argv=0x8087810) at factory.c:48

Given all the mouse configuration references in the stacktrace, and having read somewhere about someone having a similar problem being caused by a bug with their touchpad, I tried commenting out the Synaptics touchpad entries in xorg.conf.

Lo and behold, the gnome-settings-daemon problem goes away. Unexpectly, the touchpad still works. Maybe there is some sort of fallback driver for the touchpad that does not cause the crash.

hmm. bug 140485 ?

gnome-control-center (1:2.20.0.1-0ubuntu3) gutsy; urgency=low

  * debian/patches/30_extra_touchpad_config_paranoia.patch:
    - Be more paranoid when attempting to configure the Synaptics pad, in
      order to avoid crashing out on X errors (LP: #148291)
  * debian/patches/99_autoreconf.patch:
    - Remove config.h~ from the diff

 -- Matthew Garrett <email address hidden> Fri, 05 Oct 2007 10:42:57 +0100

Thanks guys! Will test this later...

That seemed to work. Updated, uncommented the Synaptics entry in xorg.conf and rebooted -- This time login proceeded without any gllitches. Of course, the mouse cursor now moves slow as molasses with the touchpad now when it was fast before, but that's a different issue, and a minor one.

Thanks!

Tested on Oct 9, 2007 using the "daily-live" [Gutsy] iso from Oct 9, and still get the error:
"Unable to start the settings manager 'gnome-settings-daemon'.
Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with Bonobo, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager."
when trying to change the background.
After selecting "OK" the "Appearance Preferences" gui is displayed.

I too have experienced this problem after the last update (tonights, 40 packages including 2.6.22.14 kernel headers etc..)

There was an error starting the GNOME Settings Daemon

Some things, such as themes, sounds, or background settings may not work correctly.

The last error message was:

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.
There was an error starting the GNOME Settings Daemon

GNOME will still try to restart the Settings Daemon next time you log in.

Mine happened after changing the audio conferencing sound capture device from alsa to Nvidia 2. My desktop froze and and then the 3d desktop disappeared along with the transparency. I wen to the appearance section and found that the visual effects setting had been reset to none. I re-enabled custom effects and my 3d desktop came back with all the trimmings but I rebooted anyway just to be sure everything was back to normal, thats when I got the above message
(on login to ubuntu root desktop). All seems to be okay except the text on all tool bars has become very small and also some of the icons have changed, such as the one to shut down/logout the user which is now a green man on the run as opposed to the usual power button icon. Also I'm getting that box come up if I try to enter the sound setting box or any item on the preferences menu although they selected item does appear after clicking ok on the error box

Also I tried running the gnome-settings-daemon in the terminal and my toolbar fonts and theme came back, however the the command did not complete and hung with this message......

 gnome-settings-daemon

** (gnome-settings-daemon:6588): WARNING **: Unable to connect to dbus: Failed to connect to socket /tmp/dbus-iBoaXqH3T7: Connection refused

(gnome-settings-daemon:6588): GnomeKbdIndicator-WARNING **: Unable to connect to dbus: Failed to connect to socket /tmp/dbus-iBoaXqH3T7: Connection refused

(gnome-settings-daemon:6588): GnomeKbdIndicator-WARNING **: Not connected to dbus, will not register the object
xrdb: "*Label.background" on line 220 overrides entry on line 150
xrdb: "*Text.background" on line 226 overrides entry on line 191
xrdb: "*Label.foreground" on line 232 overrides entry on line 151
xrdb: "*Text.foreground" on line 238 overrides entry on line 192

** (gnome-screensaver:6595): WARNING **: failed to register with the message bus

In my case problem was in package libtag from rusxmms project.
Gnome-settings-daemon hanging was caused by gstreamer hanging, and gstreamer hanging was caused by libtag.
After installing libtag from ubuntu repository, problem has gone.

gnome-control-center (1:2.21.2-0ubuntu1) hardy; urgency=low

  * New upstream version:
    about-me:
    - Add another string to the list of recognized error returns from passwd
    - Don't get confused when the user does not have a password set and passwd
      immediately asks for the new one
    appearance:
    - Fix build without libXcursor
    - Be more careful when reading background information from GConf and
      make sure we don't choke on NULL values later on
    keyboard:
    - Fix warnings and don't use deprecated signal API from GTK
    - Move layout options to separate popup
    - Rename first tab to "General"
    - Replace text entry and "Choose.." button for keyboard model with a
      single chooser button
    - Don't include keyboard model description in Glade file
    localization:
    - Added (very basic skeleton of) localization capplet
    shell:
    - Remove reference to non-existing background.desktop
    settings daemon:
    - Make composited media popup window sizes scale with the screen size
    common:
    - Remove more redundant info from the theme changed callback
    updated translations
    appearance:
    - Unify "invalid theme" error messages and be a bit more verbose
    - Reword the "theme engine" error message
    - Add support for dragging images from the background list
    - Make theme sorting case insensitive
    - Fix crash if we fail to convert a filename to UTF-8
    - Use NoDisplay=true instead of OnlyShowIn=; (LP: #152453)
    - Return a new theme instead of munging whatever got passed in
    - Take cursor size into account when comparing themes
    - Watch cursor theme/size GConf keys for changes
    - Move cursor size widget initialization to Glade, to allow the slider to
      be updated properly on startup
    - Make the cursor themes delete button works
    - If the parent directory is empty after deleting a theme, delete the
      parent directory too
    - Update cursor size GConf value when the theme changes
    - Reduce number of XCURSOR ifdefs and get rid of the special treatment for
      the default cursor theme
    - Add support for live cursor theme updates
    - Read gettext macro that accidentally got stripped
    - Prevent lots of thumbs from being created with the color scheme of the
      currently active theme
    - Actually remove theme data from the hash when the theme gets deleted
    - Fix the cursor size only being updated if the cursor theme changed too
    - Watch /usr/share/cursors/xorg-x11 for cursor themes
    - Teach the installer to recognize cursor themes and icon themes with
      cursors
    - Check whether there are multiple themes to install up front
    at-properties:
    - Don't use 'Preferences' word for application name
    default applications:
    - Make the accelerators for the A11Y tools page unique
    - Replace mail and multimedia icon names with Tangoified versions
    - Use standard xdg autostart directory instead of GNOME one
    - Replace obsolete 'orca -m' command with new 'orca -e magnifier'
    display:
    - Code cleanup and fix a few leaks
    - fix string capitalization
    fontilus:
    - Drop "GNOME" from the menu item name as recommended...

I'm having this problem after upgrading from 8.04 to 8.10

same symptoms, no audio icon (and can't add it), re-installed compiz and gnome and still nothing, I get this "old-look" windows and that error message when opening the theme settings (and even if I change them, the colors change a bit, but not the theme or icons).

I tried with safe gnome, same problem.

I did had some trouble in the upgrading process, I was using "half-intrepid" for a while, and this happened when today I installed everything it asked me to in the update manager :)

i have the same problem as eNz1m3mit happen when i try to update my 8.10 beta.after restart..it all happen.any solution?

eNz1m3,try to update ur ubuntu.i just update n restart.suddenly,they all fixed!

There's nothing to update (no updates available, all done, I rebooted several times, reinstalled gnome, compiz and compiz-core)...

Ok,

So today morning there was an upgrade related to audio (didn't catch the name), after that, I could add the volume control icon and change theme successfully :)

Thank you for your time.

I'm having the exact same issue with updated Intrepid. After first login I get no theme. I have to log out and re-login to get the proper theme. I also get a seahorse-agent crash report (similar to bug #282663 ), I don't know if these two are related somehow. Please let me know if you need any logs.

you have no indication that's the exact same issue, open a new bug rather than reopening a closed one

I also get the same error message as the original reporter when I try to start the appearances menu:

Unable to start the settings manager 'gnome-settings-daemon'.
Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with Bonobo, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager.