FS#36009 - gnome-settings-daemon causes hang of gdm

Attached to Project: Arch Linux
Opened by Peter Weber (hoschi) - Wednesday, 03 July 2013, 11:36 GMT
Last edited by Jan de Groot (JGC) - Monday, 08 July 2013, 08:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


The startup of GDM fails sometimes, approximately once in ten times. The cause seems to be a typically random occuring race-condition. If a race-condition happens, GDM will hang for ~ 30 seconds and will be later restarted. The people at Fedora discovered it during testing for Fedora 19 and declared the issue to a blocker. The workaround seems to be the usage of an external shell-script.

Additional info:
* package version(s): gnome-settings-daemon >= 3.8.0
* sources:
https://bugzilla.redhat.com/show_bug.cgi?id=919855 # they seem to use a workaround with a shell script (mentioned in the llink below)
https://bugzilla.gnome.org/show_bug.cgi?id=701322 # upstream solution, also based on the shell-script

Steps to reproduce:
1. Reboot machine to GDM-Login
2. Repeat this often, until you hit the bug -> Login hangs
3. dmesg prints something like this: dconf worker[1016]: segfault at 3ed1 ip 00007fb77031f72d sp 00007fb760e6e6a0 error 4 in libc-2.17.so[7fb7702e7000+1b5000]
4. journalctl -b will show after a half minute or so that it killed the login and restarts it

It looks like the people at GNOME want to stay with the workaround based on the shell script, at least for now. I hope the rewrite the responsible code in gnome-settings-daemon in future.
Thank you

I really wonder why nobody else reported this bug in the past months anywhere :-)
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 08 July 2013, 08:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  Added post-release fixes for this from gnome-3-8 branch in 3.8.3-2.
Comment by Gunnar Waterstraat (hansmitdampf) - Thursday, 04 July 2013, 07:31 GMT
I am experiencing the same, after a clean install of Arch two days ago. However - just as *hoschi* it is typically occuring randomly. Didn't have it once yesterday while being twice in a row just right now.