[Gutsy]gnome settings daemon not started, default human theme changed

[Neville Makopo]

Binary package hint: libgnome-settings-daemon-dev

On Ubuntu Gutsy Tribe 5
During a restart after login the default Human theme had changed and the first(1) message below was displayed.
Trying to change the theme back to Human by right-click - Change Desktop Background, message (2) is displayed. What is weard is that Human is already selected but my desktop still looks blue. I'm not sure whether this bug is related anyhow to bug reports like #84876. Also most bugs of this nature seems to be a result of an upgrade from feisty, but this just Gutsy.

(1)
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.

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

(2)
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.

[Neville Makopo (kompressor)]

attached is the output of dmesg command after login.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Looks like a problem caused by a not running dbus. Its your loopback network working?

[Neville Makopo (kompressor)]

Thanks, I think you're right, I double checked that dbus was not running and my loopback is working.
I have not been able to see the problem again.
thank you again

[Sebastien Bacher (seb128)]

closing the bug then, feel free to reopen if you get the issue again though

[Jeff Fortin Tam (kiddo)]

Wait. This bug hit me today. How do I provide information?

[Jeff Fortin Tam (kiddo)]

If I try to run it in a terminal after being logged in:

jeff@kaname:~$ 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 769 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.)
[1190069177,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application

[Jeff Fortin Tam (kiddo)]

Nevermind. Seems like the problem was the synaptics touchpad package, which is being uploaded as i write. I tested the version in this thread [1] and it works, so sorry for the spam.

[1]: http://ubuntuforums.org/showthread.php?t=553094

[Ivan Ivanoff (spammeroff)]

I have this problem after installing xserver-xgl and deleting it. I get this error and cannot start gnome-settings-daemon again and here is a log:
** (gnome-settings-daemon:6075): 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:6075): 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:6075): GnomeKbdIndicator-WARNING **: Not connected to dbus, will not register the object
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 symbols defined for <K59> (keycode 157)
Warning: No symbols defined for <I1E> (keycode 158)
Warning: No symbols d...