Ubuntu
kdeartwork package

kscreensaver does not respect SimulateUserActivity dbus method

Bug #310352 reported by Al Williams
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KDE Artwork
Fix Released
Medium
kdeartwork (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: kscreensaver

lsb_release -rd -> Ubuntu 8.10
Using Kubuntu

SimulateUserActivity should deactivate screensaver as though the user poked some keys. But this doesn't work.

The following should trigger the screensaver, wait 5 seconds and then unstick the saver (maybe prompting for a password). Instead the saver stays active until the user moves the mouse or presses a key.

$ dbus-send --print-reply --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.SetActive boolean:true ; sleep 5 ; dbus-send --print-reply --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.SimulateUserActivity

See original description
Al Williams (wd5gnr)
description: updated
Revision history for this message
Sybren Stüvel (sybren-stuvel) wrote :

I can confirm this bug, and provide some output. This is on Kubuntu 9.04 development branch up-to-date as of 14:00 CET today.

$ dbus-send --print-reply --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.SetActive boolean:true
method return sender=:1.24 -> dest=:1.115 reply_serial=2
   boolean false

$ dbus-send --print-reply --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.SimulateUserActivity
method return sender=:1.24 -> dest=:1.116 reply_serial=2

Changed in kdeartwork:
status: New → Confirmed
Revision history for this message
Sybren Stüvel (sybren-stuvel) wrote :

If the screensaver was activated by lack of user activity (as opposed to the above DBUS call to SetActive(true)) then calling SimulateUserActivity() does have the proper effect of deactivating the screensaver.

Revision history for this message
Bernardo Kuri (accounts-bernardokuri) wrote :

I can also confirm this happens under Kubuntu 9.04 amd64. I am running blueproximity with the following commands (under the "Locking" tab):

Locking command: qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock
Unlocking command: qdbus org.freedesktop.ScreenSaver /ScreenSaver SimulateUserActivity
Proximity command: qdbus org.freedesktop.ScreenSaver /ScreenSaver SimulateUserActivity

The locking command works great, the other two don't.

Harald Sitter (apachelogger)
Changed in kdeartwork (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Jonathan Thomas (echidnaman)
Changed in kdeartwork:
importance: Undecided → Unknown
status: New → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in kdeartwork:
status: Unknown → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in kdeartwork:
status: Confirmed → Won't Fix
Revision history for this message
Harald Sitter (apachelogger) wrote :

Wontfix as per upstream. Please refer to the bug at bugs.kde.org (as linked above) for further discussion of this topic.
Thanks.

Changed in kdeartwork (Ubuntu):
status: Triaged → Won't Fix
Bug Watch Updater (bug-watch-updater)
Changed in kdeartwork:
status: Won't Fix → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in kdeartwork:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.