Red Hat Bugzilla – Bug 963129
gnome-screensaver reveals desktop when screen is locked
Last modified: 2014-02-05 16:22:28 EST
Description of problem:
gnome-screensaver reveals desktop when screen is locked and network manager prompts for wi-fi password
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. laptop placed in dock-station, laptop display turned on, second display connected from dock-station via hdmi, both displays in full-hd resolution
2. enable wi-fi in area with known wi-fi network which prompts for password every time
3. cancel password prompt and lock screen
after ~5 min, when network manager asks for wi-fi password again, the screen, which had mouse focus when locking, reveals it's content, the second screen stays off.
screen shouldn't show anything when locked
This might be a duplicate of Bug 906126. I am also wondering if it makes a difference if Nautilus is managing the desktop?
Also, is this just the background image of the desktop, or desktop icons and open windows and stuff? I'm seeing the background image in the screensaver in Fedora 19 but haven't seen anything else recently, so this might be fixed in 19.
I some form, it might be duplicate of metioned bug, however, it behaves a little bit differently.
The screen is revealed when some window is showed up while the screen is locked, in my case, it's happening when the network manager prompts for password, or when thunderbird pops a calendar notification.
These are not being shown, the screen reveals exactly what was there when the screen was locked (being it browser, terminal, mail client, whatever). Then I need to type password blindly (no prompt for password) and after unlocking, the window which triggered this (wifi pwd, thunderbird notification, etc.) shows up - from this I suppose that the popup is the culprit.
I use dual screen and only the one which shows the prompt is revealed (mouse focus?) the other stays off.
I can send you a "screenshot," if you want.
Not using Nautilus, but Nemo, so there might be the same bug.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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
Thank you for reporting this bug and we are sorry it could not be fixed.