Bug 207058
Summary: | "Lock" in workrave stayed locked forever, even after entering a password | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stewart Adam <s.adam> |
Component: | workrave | Assignee: | Tomas Mraz <tmraz> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | extras-qa, mszpak, rstrode, triage |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-03 15:49:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Stewart Adam
2006-09-19 00:20:37 UTC
When xscreensaver is installed instead of gnome-screensaver it works fine. CCing Ray if he has some insight on this. gnome-screensaver does this: do { result = gs_grab_move_keyboard (grab, window, screen); gdk_flush (); } while (!result); do { result = gs_grab_move_mouse (grab, window, screen, hide_cursor); gdk_flush (); } 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? Reported upstream: http://issues.workrave.org/cgi-bin/bugzilla/show_bug.cgi?id=726 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: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. nevermind comment #5 :) |