[Bug 34793] spice client doesn't inhibit screensaver properly

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=34793

--- Comment #10 from David Mansfield <freedesktop-bugzilla at dm.cobite.com> ---
I've been pointed (correctly) to this bug from the list.  My issue adds another
wrinkle.  I run spice full-screen on one monitor (actually two) but the other
monitor is "local".  So inhibiting the screensaver means leaving all that
information visible - indefinitely.

Additionally, since there is no activity being sent to local screensaver, the
minute the mouse moves out of the "spice monitor" the screensaver locks, even
though I typed a key 1 second ago.

Maybe this all works in GNOME, but I use MATE.  I should test it.  Anyway,
since this bug is open, I assume it's still a problem everywhere.

I think two things fix this:

1) "poke" the local screensaver when there is "activity" in the spice window. 
this could be a) every mouse and keyboard event, b) once per "time quantum", or
c)"just-in-time" before local screensaver locks, but I think c) sounds
horrendously difficult for no benefit

2) via the guest agent, integrate with guest screensaver.  when it blanks
and/or locks, release mouse/keyboard grab.  if the local screensaver is ready,
it will immediately lock simultaneously.  Yes, the user will have a double
screen-unlock to deal with. Maybe another agent message could take care of that
and unlock the guest screensaver when local is unlocked, but that is a feature
for another day.

One additionaly thing: the guest agent should lock the guest screensaver on
disconnect.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/spice-bugs/attachments/20150115/f38ee97f/attachment.html>