Bug#614682: Trouble with settings daemons at startup
Le samedi 09 avril 2011 à 14:22 +0200, Cyril Brulebois a écrit : However the X server does not properly clean up its state immediately, leading to a race condition. If the startup is very fast (which is usual for Xfce users or SSD owners), the new settings daemon receives wrong information from the X server that a settings daemon is still running, while actually it is not. since you kind of know what's happening, I'd appreciate if you could open a bug upstream directly: https://bugs.freedesktop.org/ product=xorg, component=Server/general I have received more explanations from Ryan Lortie, and it might not be as simple as “a bug in the X server”; although the problem probably lies in the interaction between the Xsettings manager and the X server, it might not be possible to actually fix it on the X side (which would mean the Xsettings specification has a design flaw). IMHO more testing is required before involving X people. You might want to reassign this to gdm3 in the meantime, since although this is not a bug in gdm3, it is the package that exhibits it. -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you are blackmailed by someone, `-[…] I will see what I can do for you.” -- Jörg Schilling signature.asc Description: This is a digitally signed message part
Bug#614682: Trouble with settings daemons at startup
clone 614682 -1 -2 forwarded 614682 https://bugzilla.gnome.org/show_bug.cgi?id=634988 reassign 614682 gnome-settings-daemon reassign -1 xserver-xorg-core retitle -1 X server incorrectly reports a running settings daemon reassign -2 xfce4-settings retitle -2 xfce4-settings-daemon should try again when X reports a running Xsettings manager thanks The upstream bug linked here ^ explains what is happening. It is not a bug in gdm3, which properly waits for gnome-session to exit (which in turns waits for gnome-settings-daemon) before launching anything. However the X server does not properly clean up its state immediately, leading to a race condition. If the startup is very fast (which is usual for Xfce users or SSD owners), the new settings daemon receives wrong information from the X server that a settings daemon is still running, while actually it is not. GNOME upstreams applied an ugly workaround in gnome-settings-daemon, which consists in waiting 20 times 0.1 second, checking whether it can start: http://bugzilla-attachments.gnome.org/attachment.cgi?id=184538 You might want to do the same in xfce4-settings until the X server is fixed (or until the Xsettings specification is updated to not rely on a racy mechanism). Cheers, -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you are blackmailed by someone, `-[…] I will see what I can do for you.” -- Jörg Schilling signature.asc Description: This is a digitally signed message part
Bug#614682: Trouble with settings daemons at startup
Hi, Josselin Mouette j...@debian.org (09/04/2011): The upstream bug linked here ^ explains what is happening. It is not a bug in gdm3, which properly waits for gnome-session to exit (which in turns waits for gnome-settings-daemon) before launching anything. However the X server does not properly clean up its state immediately, leading to a race condition. If the startup is very fast (which is usual for Xfce users or SSD owners), the new settings daemon receives wrong information from the X server that a settings daemon is still running, while actually it is not. since you kind of know what's happening, I'd appreciate if you could open a bug upstream directly: https://bugs.freedesktop.org/ product=xorg, component=Server/general (I have neither a SSD or a fast enough machine to reproduce this.) KiBi. signature.asc Description: Digital signature
