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 427793 - No support for KDE screensaver
No support for KDE screensaver
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
git master
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 503072 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-04-09 08:19 UTC by Rodrigo Moya
Modified: 2008-03-22 11:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rodrigo Moya 2007-04-09 08:19:19 UTC 
People running other desktops than GNOME are autostarting gnome-settings-daemon in order to have GNOME/GTK applications (firefox and thunderbird mainly) use the same font's DPI and sizes in both KDE and GTK applications.

It is of course not a good solution having to autostart g-s-d, but until we find a better way, g-s-d should be able to deal with the situation. Right now, it looks for gnome-screensaver in $PATH, if found, it uses it, if not, it falls back to xscreensaver, so I guess we could add code to detect if it's running on another desktop and if so, not start any screensaver at all.
Comment 1 Jens Granseuer 2007-08-17 18:31:58 UTC 
It might be better to check whether a screensaver is already running rather instead of trying to identify the DE.
Comment 2 Jens Granseuer 2007-12-16 10:43:27 UTC 
*** Bug 503072 has been marked as a duplicate of this bug. ***
Comment 3 Jens Granseuer 2007-12-16 10:44:31 UTC 
or, from bug 503072:

"I just had a very odd experience. I was running a kde session on machine a,
opened an ssh -Y connection to machine b, and ran a rhythmbox from there (to
test some statusicon stuff). I killed rhythmbox and went on to do something
else.
When I came back after a while, I was surprised to find machine a locked,
by gnome-screensaver from machine b !

Quick analysis: running rhythmbox starts gnome-settings-daemon (for multimedia
key handling), which in turn starts gnome-screensaver (on the ssh-forwarded
display).

Ray and I think that the bug here is that activating gnome-settings-daemon has
the side-effect of starting gnome-screensaver. It should not do that, instead
gnome-screensaver should be a regular autostarted app."
Comment 4 Jens Granseuer 2008-03-13 21:11:34 UTC 
With the new g-s-d, this is now obsolete. The screensaver plugin can simply be turned off for users who don't want it.
Comment 5 Vincent Untz 2008-03-20 19:56:07 UTC 
Hmm, I disagree with closing as OBSOLETE: if I run both GNOME and KDE, depending on my mood, I don't want to disable some plugin each time I log in KDE and enable the plugin again when I log in GNOME. We should do more.

Can we reopen the bug?
Comment 6 Jens Granseuer 2008-03-22 09:39:38 UTC 
Sure we can. The fix, then, is to simply remove the g-s-d module and make the screensaver a regular auto-started app, so it would be, what, gnome-session responsibility? Feel free to take it, Vincent. ;-)
Comment 7 Vincent Untz 2008-03-22 11:31:59 UTC 
I'll look at it. Should be trivial, just needs time :-)