Red Hat Bugzilla – Bug 207058
"Lock" in workrave stayed locked forever, even after entering a password
Last modified: 2008-04-03 21:39:18 EDT
Description of problem:
When performing a timeout and clicking "Lock", gnome-screensaver if enabled but
after the passwored is typed and gnome-screensaver is disactivated, the screen
remains black. I have to switch VT's and kill workrave.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Click the teacup to start a timeout
2. Click "Lock"
3. Enter your password
The screen remains black / locked, even though gnome-screensaver's gone
When xscreensaver is installed instead of gnome-screensaver it works fine. CCing
Ray if he has some insight on this.
gnome-screensaver does this:
result = gs_grab_move_keyboard (grab, window, screen);
} while (!result);
result = gs_grab_move_mouse (grab, window, screen, hide_cursor);
} while (!result);
One of those two loops isn't ever breaking while workrave is running and that's
why gnome-screensaver isn't unlocking until you kill workrave.
is workrave grabbing the keyboard after unlocking the screen? There may be a
race there or something
Yes, workrave tries to grab the keyboard and mouse after 2s with 2s intervals
after it calls gnome-screensaver-command to lock the screen. It needs to grab it
for the workrave's rest break window. Is there any way how it could wait for the
gnome-screensaver to be unlocked and try to grab just after that?
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
nevermind comment #5 :)