Red Hat Bugzilla – Bug 1092857
gnome-screensaver takes 30+ seconds to unlock
Last modified: 2016-08-03 11:34:37 EDT
Description of problem: It takes very long to get the display back after running Gnome Screensaver for more than 15 minutes. Version-Release number of selected component (if applicable): gnome-screensaver-2.28.3-28.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. Start gnome screensaver and keep it running for more than 15 minutes. 2. Wake up the screensaver by moving mouse. Actual results: It will take more than 30 seconds (sometimes minutes) to get the display back. Expected results: Screensaver should wake up within seconds. Additional info: System has 2 nvidia quadro fx 580 graphics cards with 3 monitors.
Created attachment 891036 [details] Fix repeated deactivation requests Avoid queueing up deactivation requests while the screensaver is waking up.
Comment on attachment 891036 [details] Fix repeated deactivation requests Looks good
I suffer this issue running CentOS 6.5 x86_64. If you want the patch testing externally, could you allow access to the patch and I will happily test it.
Hi Phil, I have made the patch public.
Thank you for making the patch visible. I compiled the patch into 'gnome-screensaver-2.28.3-28.el6.x86_64' on an affected CentOS 6.5 (with all updates). The patch applied and package built via mock with no issues. Prior to package install I checked the bug was still active on my system. It was. Post installation of the updated package, I activated the screensaver on multiple occasions through the day/evening and allowing it to be active for > 15 mins. The longest time period was an hour. Attempts to deactivate the screensaver using mouse movement were successful and never took longer than a couple of seconds. This is much better than the long waits previously. The patch fixes the issue for me.
Hi Phil, Thanks for reviewing the patch. We are working to make this fix available in RHEL 6.6.
Would it be possible to see the bug that is blocking this update?
it's just an internal tracking bug with no comments on it. it's used for internal workflow processes, there's nothing interesting on it.