After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 344069 - Per-DISPLAY initialisation of gnome-settings-daemon fails
Per-DISPLAY initialisation of gnome-settings-daemon fails
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
2.14.x
Other Linux
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-06 21:08 UTC by Jan de Groot
Modified: 2006-10-15 00:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Jan de Groot 2006-06-06 21:08:03 UTC 
Since gnome 2.14.0, the gnome-settings-daemon is registered per display. This causes problems in these situations:

- running multihead display, DISPLAY can be either :0.0, :0.1 or :0. gnome-settings-daemon takes care of all 3 of them as xsettings manager, which means a 2nd or 3rd daemon can't start for the same DISPLAY

- starting gnome, quitting it and starting it quickly again: bonobo won't start a new gnome-settings-daemon because a session is already present for $DISPLAY. However, since it got a killed X DISPLAY reference, it will not do its work and report failure.

This is caused by the last two commits in gnome-settings-daemon/factory.c. The related bugreport states that no regressions were found, but they were hidden by another bug, which has been fixed in 2.14.1.

The method used to register per $DISPLAY using bonobo is wrong. Bonobo will do strict checking on the environment variable. When the variable isn't the same, it will spawn another daemon, which doesn't work in the above cases.
Comment 1 Jan de Groot 2006-10-15 00:04:04 UTC 
Fixed in 2.16, this is no longer an issue with the dbus based gnome-settings-daemon.