Bug 181882
| Summary: | desktop locks immediately after changing the system clock | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Juergen Bullinger <juergen.bullinger> |
| Component: | glib2 | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | chris.brown, demon, frank, hdegoede, jmccann, sundaram |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-08-28 03:16:15 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 150223, 197822 | ||
|
Description
Juergen Bullinger
2006-02-17 13:45:30 UTC
These bugs are being closed since a large number of updates have been released after the FC5 test1 and test2 releases. Kindly update your system by running yum update as root user or try out the third and final test version of FC5 being released in a short while and verify if the bugs are still present on the system .Reopen or file new bug reports as appropriate after confirming the presence of this issue. Thanks Hi, this problem still exists in fc 5 Test 3 (I detected it in FC5 Test 2 and changed the version info to FC 5 Test 3) I guess you set a timer and check after this timer fired if there was user activity since setup of the timer. If it works this way you can probably avoid this behaviour in a very simple way. Separate your timer period in two periods. If the first is without activity then set up a second timer (maybe using a smaller period) if there is also no activity in this period you can switch on the screenshaver. You probably just need to change your logic so that it waits two periods of time. If you use a "hook" on mouse events and stuff it's similar. If you haven't received any event during a timer period you also can setup a timer for a "last call". If the user also doesn't do anything in this period it is pretty save to switch the screensaver on. If you can manage to detect clock skews, I would really like to see the sourcecode :o) Hi sorry, I changed the status to "NEEDINFO", because I don't know what exactly "REOPEN" means it looks like probably you haven't recognized that I still have this problem and added some new info (see above) *** Bug 186800 has been marked as a duplicate of this bug. *** Just too funny. I filed it upstream: http://bugzilla.gnome.org/show_bug.cgi?id=336114 Hmmm, This becomes somewhat less amusing with U.K. users entering British Summer Time therefore clocks have jumped forward one hour. I am seeing this on a fully updated system under FC5. I have attempted to disable screen blanking on the power controls (following inactivity) however it continues to blank every 20 minutes. Regards Chris Upstream bug has a patch that I'm going to put into glib, we should put that in our glib package, too. Fixed in glib-2.12.2-2.fc6 |