Description of problem: If inactivity allows the Blank Screen to activate, display switches to power-save mode and session is unrecoverable. Manually refreshing the display does not work, no keyboard shortcuts work, and tower must be power-cycled. No proprietary drivers are installed, no custom wallpapers or screensavers. Version-Release number of selected component (if applicable): $ cat /etc/redhat-release ; uname -a Fedora release 21 (Twenty One) Linux My.domain.com 3.17.8-300.fc21.x86_64 #1 SMP Thu Jan 8 23:32:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux * AMD Phenom(tm) 9550 Quad-Core Processor × 4 * Graphics: Gallium 0.4 on NVA8 * Gnome: Version 3.14.2 * GeForce 8400GS 1GB PCI Express 2.0 Video Card How reproducible: Consistently. I am able to isolate that the problem DOES NOT occur with the Gnome Privacy "Lock Screen," but ONLY with the Power Saving setting (or a combination of the two). Steps to Reproduce: 1. Allow default desktop Gnome Configuration 2. All inactivity timer to reach "Blank Screen" setting threshold. Actual results: Display (monitor) goes into power-save mode and user session becomes unrecoverable. Expected results: Moving mouse (and dragging up) should wake the display and prompt user for Screen Lock password. Additional info: Seems most like <https://bugzilla.redhat.com/show_bug.cgi?id=769447>, but problem presents with fresh install (non-upgrade) of fedora21. Disabling the Gnome Settings > Power > Power Saving > Blank Screen to "Never" fixes/avoids the problem. Super+L shortcut and manual screen lock is not a problem, even if the display is allowed to sleep afterwards. Problem seems isolated to the Power Saving settings.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I want to reopen this bug for fedora 24. The bug hasn't happened in fedora 23, but now I can report the same problem.
seems I am seeing something similar in Fedora 23. Should I reopen a new bug?
No response to my query of three years ago. Bug report no longer relevant. Am clearing the needinfo flag.