GNOME Bugzilla – Bug 411754
Rhythmbox launches gnome-screensaver
Last modified: 2007-02-26 16:55:22 UTC
Please describe the problem: Launching Rhythmbox in a non GNOME environment results in a bunch of GNOME apps being called, including gnome-settings-daemon and gnome-screensaver. This results in a conflict with xscreensaver which I use by preference. I will attach a "ps" output from before and after. Steps to reproduce: 1. Open a non-GNOME environement. 2. Run 'ps' to see that gnome-screensaver is not running. 3. Run rhythmbox 4. Run 'ps' to see that gnome-screensaver is now running. Actual results: gnome-screensaver and a bunch of other un-needed programs are launched. Expected results: I would expect the necessary infrastructure to be launched for rhythmbox to function. I DO NOT think a screensaver is essential to the running of rhythmbox. This makes rhythmbox unusable in a non-GNOME environment. Does this happen every time? Yes, unfortunately. Other information: This has been reported at: https://launchpad.net/ubuntu/+source/rhythmbox/+bug/87591
Created attachment 83281 [details] ps command before rhythmbox is launched
Created attachment 83282 [details] ps command after rhythmbox is launched
Rhythmbox definitely shouldn't cause gnome-screensaver to start. I use Gnome on my machine, and gnome-screensaver isn't started when I launch Rhythmbox - so it's possible that gnome-settings-daemon is what is starting it.
gnome-settings-daemon starts the screensaver. Setting the gconf key /apps/gnome_settings_daemon/screensaver/start_screensaver to false appears to stop it from doing so. Alternatively, uninstalling gnome-screensaver will cause it to use xscreensaver instead. I don't see how this makes rhythmbox "unusable in a non-GNOME environment". If this behaviour actually caused you a serious problem (and "some extra processes are running" is not a serious problem), you didn't explain it very well.
Jonathan, I described this as a serious problem because both gnome-screensaver and xscreensaver end up running and if I forget to kill gnome-screensaver they both end up activating and many times this causes xorg to hang on my machine. On about 6 occasions this week I have had to give xorg the three fingered salute because of this an lost my work each time in the process. Is there anyway to get gnome-settings-daemon NOT to launch gnome-screensaver (or any other user apps like this) when invoked from another app by default WITHOUT playing around with gconf? The only reason I ask is that anyone who wants to use a GNOME app in another window manager (ion3 in my case) will experience this weird behaviour of two screensavers running, and perhaps (albeit a little more unlikely) experience the same xorg problems as me. I doubt that most users would feel motivated enough to pursue this as far as I have, let alone know or understand how to play around with gconf.
I'd say this is up to the distros or to gnome-settings-daemon to handle that more gracefully (ie this bug can probably be moved somewhere else)
Can you advise how to file a bug against gnome-settings daemon as your bug tracker does not seem to know anything about it.
Noah: what version of rhythmbox are you using? If you are using a recent version if you go into gconf-editor and deactivate /apps/rhythmbox/plugins/mmkeys/active does the problem go away? Also, gnome-settings-daemon is in the gnome-control-center module. It appears that gsd installs a dbus service file...