+++ This bug was initially created as a clone of Bug #896633 +++ This might be the same bug, but I am not sure, so hence the clone. Also, this is on Fedora 17. I relatively frequently experience the same as the original reporter, but have not found a time limit before it occurs. The effect is the same: After the machine has been inactive for some time, when activating the machine by moving the mouse or pressing a key, the background image is displayed, but the password dialog is never displayed. The time it takes before this happens varies; sometimes overnight and sometimes much shorter. It does not happen every time either. Previously I powered down the machine to solve this, but today I found a workaround that might be helpful in locating the source of the problem. This is what I did: 1. Open a vertual terminal (Ctrl-Alt-F2) 2. Log in as root 3. startx 4. Start System Monitor (Gnome's) 5. Set it to "show all processes" and "Show dependencies" 6. Locate the process tree pertaining to the other user, find "gnome-screensaver" 7. There was a child process of "gnome-screensaver" called "gnome-screensaver-dialog"; kill it. 8. Go back to the main session (Ctrl-Alt-F1) 9. The password dialog is displayed and it is working. -------- Original description of problem: When I leave my laptop locked for a longer period (my current estimate is more than 15 minutes) the password entry dialog does not appear after I have slided up the screensaver screen that is displayed as of F18. Currently I have to turn off the laptop with the on/of switch and reboot to have a working environment again. Version-Release number of selected component (if applicable): Installed Packages Name : gnome-screensaver Arch : x86_64 Version : 3.6.1 Release : 1.fc18 Size : 1.1 M Repo : installed Summary : GNOME Screensaver URL : http://www.gnome.org License : GPLv2+ Description : gnome-screensaver is a screen saver and locker that aims to have : simple, sane, secure defaults and be well integrated with the : desktop How reproducible: By locking the laptop and leaving it unattended for at least 15 minutes Steps to Reproduce: 1.Lock screen 2.Leave unattended for 15 minutes 3.Slide up "screensaver screen" Actual results: Normal behavior is that the "unlock screen" appears after sliding up the screensaver screen. When the problem occurs only a black screen appears. Also entering the password "in the blind" does not unlock the screen. Expected results: "Unlock screen" appears so password can be entered and system is unlocked Additional info: Currently none. If more info is required please let me know. --- Additional comment from Resa Drijsen on 2013-01-18 07:07:22 EST --- Today I encountered the same issue again. In an attempt to see whether I could stop the screensaver "manually" I entered a terminal using <Ctrl>-<Alt>-<F2> and logged in. However, I could not find a running process that I could relate to the screensaver. What I did come across is the following (result of "ps -ef | grep watch-log): root 808 1 0 09:36 ? 00:00:00 /usr/bin/abrt-watch-log -F BUG corruption stack overflow protection fault WARNING: at nable to handle ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed INFO: possible recursive locking detected : nobody cared IRQ handler type mismatch /var/log/messages -- /usr/bin/abrt-dump-oops -xD root 809 1 0 09:36 ? 00:00:00 /usr/bin/abrt-watch-log -F Backtrace /var/log/Xorg.0.log -- /usr/bin/abrt-dump-xorg -xD I have no idea whether or not it is related to this issue but it seemed better to provide the info than to withold it. --- Additional comment from Resa Drijsen on 2013-01-21 09:30:20 EST --- Today I encountered the same issue again, however it ONLY seems to happen when I have a VirtualBox image also open. Today I had Win7 running in VBox when the issue re-appeared. Hopefully this helps in reproducing the error.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.