Hide Forgot
Description of problem: If XFCE is suspended, the system enters hibernation and the display is disabled before any screensaver is activated. When the system is resumed the display is activated and the contents of the screen are shown until the fade-out and the screensaver activates. This is a potential security risk as the dialog to unlock the system is not displayed until after the screensaver starts. Version-Release number of selected component (if applicable): How reproducible: Suspend system then resume. Steps to Reproduce: 1. Hibernate system 2. Resume system 3. Observe previous screen contents Actual results: Screen not blank after resuming. Expected results: Blank screen until credentials verified. Additional info: This was tested with the screensaver 'disabled'.
How can xscreensaver know that the system is going to hibernate beforehand and lock the screen before hibernation? Or when system is being activated, how can xscreensaver lock the screen before activation is going to happen? I think it is impossible.
I messed up the priority, it should be low(if a bug) as there are easy workarounds. xscreensaver likely doesn't have a bug, but I would expect the overall system to not display the desktop after a resume, if the display is locked.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.
(In reply to Mamoru TASAKA from comment #1) > How can xscreensaver know that the system is going to hibernate beforehand > and lock the screen before hibernation? Since I have the same security issue (I consider it as that) in F19, I searched for a solution and found https://wiki.archlinux.org/index.php/XScreenSaver#Automatically_lock_when_suspending.2Fsleeping.2Fhibernating In the past, Fedora applied a similar approach for KDE (since then I switched to XFCE).