gnome-settings-daemon does stop working after a random time and hangs, is not able to be killed, only a restart helps.

Bug #666015 reported by Andreas
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

I have this Bug on Ubuntu 10.04/10.10 on two different machines(one is x64, the other x86), i don't know where this comes from or how to give you information about it, but after a (random!) period of time the gnome-settings-daemon doesn't work anymore.
You can't kill it or restart it, just a restart helps. I even tried a fresh profile, same problem.

I recognize this error because first of all my media keys doesn't work anymore.
After that, when you try to change your wallpaper or something (or some keyboard settings e.g.) your always get the error:
"Der Einstellungsverwalter »gnome-settings-daemon« konnte nicht gestartet werden. Ohne den GNOME-Einstellungsverwalter werden möglicherweise einige Einstellungen nicht wirksam. Dies könnte auf ein Problem mit Bonobo oder einen bereits aktiven, nicht-GNOME- (z.B. KDE-)Einstellungsverwalter hindeuten, der mit dem GNOME-Einstellungsverwalter in Konflikt geraten ist."(sry i only have the german version.)

Another intresting point is, that conky does also stop working shortly after the gnome-settings-daemon does. But i had this error bevor i had conky, so conky doesn't produce this error.

I also thought of rythmbox, google chrome and so on producing this error, but not using on of these didn't stop the error. It always came after some time.

I also looked in dmesg, .xsession-errors etc. for errors belonging to this but i found nothing.

The only solution is a restart, because you can't stop/kill the gnome-settings-daemon anymore after it beginns to hang.

It is hard to test, because sometimes it works 10 hours and then it begins to hang and sometimes it hangs after an hour uptime.

I also found that out when it hangs:
G_DEBUG=fatal_criticals gnome-settings-daemon

** (gnome-settings-daemon:11942): WARNING **: Failed to acquire org.gnome.SettingsDaemon

** (gnome-settings-daemon:11942): WARNING **: Could not acquire name

rhythmbox also recognizes this error, errors in .xsession-errors
(rhythmbox:2528): Rhythmbox-WARNING **: Unable to grab media player keys: 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.

I also tried attching gdb to it, but didn't get that to work ..maybe someone could help.

Hope you can help me, or tell/help me how to provide more infos, i really want to know why this happens and solve it.

I really wonder why nobody ever recognized this bug, because i have it on several (different!) machines.

THx!

Version of Ubuntu: 10.04/10.10 x86/x64 (every Version produces this error)
Version of gnome-settings-daemon: 2.32.0-0ubuntu3 (i think older ones are also affected.)

Sry for bad english.

Revision history for this message
Andreas (evilandi666) wrote :

I think i can provide some additional information:

I think this has something to do with NetworkManager/or some Network .. thing, because if you often disconnect and connect your lan cable or wlan, this forces the gnome-settings-daemon to hang.
Maybe this is related to the error he describes: http://ubuntuforums.org/showthread.php?t=307741

I also can force it to hang after hibernate on several machines. Hibernate and then resume .. bam gnome-settings-daemon hangs. (But - why ever - not when you use standby (also called "suspend")).

Does anyone read this bugreport? Why is it still undecided?

Revision history for this message
sojourner (itsmealso2) wrote :

this persists into natty also , possibly is associated with NM as that has been acting flaky for me since update to natty , the same time this began to occur for me .

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Andreas (evilandi666) wrote :

Can you tell me, what is natty?

Revision history for this message
Andreas (evilandi666) wrote :

I also got this problem now after suspend, not only after hibernate as i said 2010-11-09

Revision history for this message
Andreas (evilandi666) wrote :

I tried some few things and found out, that this bug happens when your internet connection gets lost (reconnect or something) - even if your local network stays connected.
This is total weird - why does gnome-settings-daemon needs a internet connection?

Is someone caring about this bug?

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Andreas (evilandi666) wrote :
Download full text (26.6 KiB)

Hi I tried to do this,

but gnome-settings-daemon package has no debug flag equivalent package.(gnome-settings-daemon-dbg or something).

But I did some testing with gnome-settings-daemon --no-daemon --debug (killed the other instance of gsd before).

But .. you don't see any log.

PC:~$ gnome-settings-daemon --no-daemon --debug
** (gnome-settings-daemon:5294): DEBUG: Successfully connected to D-Bus
** (gnome-settings-daemon:5294): DEBUG: Starting settings manager
** (gnome-settings-daemon:5294): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-2.0/
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPluginInfo: name='X-Ressourcendatenbank' file='/usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin' location='xrdb'
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPluginInfo: name='X-Einstellungen' file='/usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin' location='xsettings'
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPluginInfo: name='Zwischenablage' file='/usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin' location='clipboard'
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/housekeeping.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPluginInfo: name='Housekeeping' file='/usr/lib/gnome-settings-daemon-2.0/housekeeping.gnome-settings-plugin' location='housekeeping'
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPluginInfo: name='Barrierefreie Tastatur' file='/usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin' location='a11y-keyboard'
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPluginInfo: name='XRandR' file='/usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin' location='xrandr'
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPluginInfo: name='Tastenkürzel' file='/usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin' location='keybindings'
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPluginInfo: name='Tastatur' file='/usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin' location='keyboard'
** (gnome-settings-daemon:5294): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin
** (gnome-settings-daemon:5294): DEBUG: GnomeSettingsPlu...

Revision history for this message
Andreas (evilandi666) wrote :

Oh .. it was kind of long, here as the output as a file...

Revision history for this message
Andreas (evilandi666) wrote :

I have to correct some things I said before. It does not hang randomly, it only hangs when internet/dsl is reconnected. (normally every 24 hours here in Germany) [lan always stays connected] and after suspend/hibernate.
And it is Ubuntu only, I tried Arch Linux, Linux Mint Debian Edition, Debian Squeeze, none of them had this problem.

Very strange thing.

I also tried to attach with gdb to it while it hangs, but this is impossible - just gdb begins to hang/wait/tries to attach.

Tell me if you need more information!

Revision history for this message
Andreas (evilandi666) wrote :

I have some new information, i finally know now what cause this problems:

I have a account at hidrive.strato.de (kind of online space) which is mounted with sshfs

Line from /etc/fstab:

sshfs#<username>@sftp.hidrive.strato.com:/users/<username> /media/HiDrive fuse uid=1000,gid=1000,umask=0,allow_other,_netdev 0 0

And when my internet reconnets, hidrive seems trying to remount it but fails at remounting and while it does that endlessly you can't use settingsdaemon .. until you do a sudo unmount -f /media/HiDrive.

So .. i don't know if this is an error in sshfs or at strato.

But I thank god, that I now know why Ubuntu does that.

I hope some one that can now help reads that.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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