[Portland-bugs] [Bug 26085] xdg-screensaver resume activates the screensaver on KDE4
Jean-Philippe André
jpeg at videolan.org
Wed Jan 20 04:18:05 PST 2010
Hello,
Le lundi 18 janvier 2010 à 05:29:39, bugzilla-daemon at freedesktop.org a écrit :
> http://bugs.freedesktop.org/show_bug.cgi?id=26085
>
> Thanks!
>
> fabo, I'm going ahead and committing this (holler at me if you had something
> else in mind).
Thanks for committing so fast.
> Now, if some kind soul could translate the (easier) qdbus calls to dbus-send
> ... :)
We're still having an issue around this "fixed" bug. Actually, the call
to Inhibit does not do anything. Indeed the calling process (qdbus) exits
immediately, and here's what the specification states:
Name: Inhibit
Args: DBUS_TYPE_STRING "application-name"
DBUS_TYPE_STRING "reason for inhibit"
Returns: INT cookie
This is a random number used to identify the
request.
Description: Request that saving the screen due to system
idleness be blocked until UnInhibit is called or the
calling process exits.
Found at:
http://lists.freedesktop.org/archives/xdg/2007-March/009187.html
(no idea at what point this reflects the actual implementation)
This kind of sucks, and the screensaver indeed activates itself after 5
or 10 minutes (note: I've not configured any kscreensaver / xscreensaver
or whatever except power management).
Using qdbusviewer (a process that does not exit), I have been able to
prevent the screensaver activation.
Sorry, I have no patch this time, I don't see any way to pass a call
from a Shell script without exiting :-(
(PS: I don't understand how the scripts are meant to work with
xdg-screensaver and xdg-screensaver.in)
Best regards,
--
Jean-Philippe André (jpeg)
More information about the Portland-bugs
mailing list