GNOME Bugzilla – Bug 671084
Screensaver warning in presentation mode under LXDE: "org.gnome.SessionManager" does not exist
Last modified: 2015-03-19 10:18:16 UTC
I am using evince version 3.2.1-3 under arch linux. I am using the lxde window manager (not gnome). Evince works great unless I enter presentation mode. In this case, the following warning appears on the command line (viewing a postscript image): ** (evince:1408): WARNING **: Problem inhibiting the screensaver: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist And (viewing a pdf): ** (evince:1435): WARNING **: Problem inhibiting the screensaver: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist I realize that evince is looking for gnome and naturally can't find it. Maybe there could be an exception in the case of using a different window manager? Thank you
Well, this is only saying that evince could not inhibit the screensaver, so in your case if you have a screensaver, it will activate even in presentation mode, so I don't think this is a bug, as it gives you a hint of why you don't get to have Screensaver inhibition.
By the way -- this still happens with 3.14.2 under arch linux (running awesome not the not so awesome gnome-session & -wm) The software tells me what I already know, without added value. This is spam. I'm not running under gnome-session. Alright, you'll fail inhibiting my screensaver, I can deal with that. After all I'm not living in a DE but forging my own fate. It would be nice for evince devs to acknowledge the use case of evince outside of gnome. To do so, do not warn that the endpoint of your dbus-RPC isn't there. It's not evince's job to manage the state of services, but rather in the dbus world, dbus & systemd will make a mess out of it on their own. It's not evince's responsibility to warn the user that the session isn't there. Think about it. If it should be there in the first place, but isn't, there's other system services who'll warn the user about it, and possibly be amidst restarting them. If it should NOT be there (evince running outside of gnome-session), then this is not an error, nor worth a warning. It's expected behaviour to not find the endpoint. Thus I suggest you just silently ignore this happening instead of printing these error messages. In both cases - you find the endpoint or you don't - The Right Thing (tm) will already happen.
this warning is coming out of GTK+ *** This bug has been marked as a duplicate of bug 693203 ***