Comment 7 for bug 726480

Revision history for this message
danmb (danmbox) wrote :

Regardless of whether gnome-screensaver is started directly, or via the dbus service -- if it finds that xscreensaver is already present, do you think it should go right ahead, or quit? I think gnome-screensaver should notice that a screensaver is already active in X and abort.

The picture you describe is not what I was talking about. Neither update-notifier nor (I believe) network-manager-gnome call gnome-screensaver directly. They don't even call the dbus org.gnome.ScreenSaver method directly. Yet somehow, indirectly, they cause dbus to start the screensaver. As I said, the common theme seems to be those small banner-like notifications ("There are 3 updates available" or "Network disconnected"). Maybe there's some common code that pops up those notices and "checks" to see if the screensaver is active -- I don't know.

So the behavior you describe (applications calling gnome-screensaver directly) has nothing to do with what I reported. I agree that this is not an LXDE bug. This is a design bug for gnome-screensaver and its dbus hook.