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 503072 - shouldn't start gnome-screensaver
shouldn't start gnome-screensaver
Status: RESOLVED DUPLICATE of bug 427793
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-11 16:36 UTC by Matthias Clasen
Modified: 2007-12-16 10:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Clasen 2007-12-11 16:36:24 UTC
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 1 Jens Granseuer 2007-12-16 10:43:27 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 427793 ***