[Portland-bugs] [Bug 17537] xdg-screensaver fails with KDE4, tries to use dcop instead of dbus
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Feb 14 23:27:37 PST 2009
http://bugs.freedesktop.org/show_bug.cgi?id=17537
Yaohan Chen <yaohan.chen at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yaohan.chen at gmail.com
--- Comment #3 from Yaohan Chen <yaohan.chen at gmail.com> 2009-02-14 23:27:37 PST ---
Here are the commands for suspend, resume, reset and lock; I don't
know how to check the status, and the reset command isn't working
for me...There is some documentation on the DBUS API at
<http://www.mail-archive.com/xdg@lists.freedesktop.org/msg03804.html>.
# suspend
cookie=$(qdbus org.freedesktop.ScreenSaver /ScreenSaver Inhibit "$$" \
"Suspending screensaver while Window $window_id is open")
# the suspense is removed when the calling process exits, so the
# script needs to fork to call it
# resume
qdbus org.freedesktop.ScreenSaver /ScreenSaver Uninhibit $cookie
# reset
qdbus org.freedesktop.ScreenSaver /ScreenSaver SetActive False
# or
qdbus org.freedesktop.ScreenSaver /ScreenSaver SimulateUserActivity
# but neither is working for me. SetActive True does launch the
# screensaver without locking though
# lock
qdbus org.kde.krunner /ScreenSaver Lock
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Portland-bugs
mailing list