After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 593729 - screensaver does not lock out all parts of gnome-shell when using dual-head
screensaver does not lock out all parts of gnome-shell when using dual-head
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: High major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on: 593060
Blocks:
 
 
Reported: 2009-08-31 22:34 UTC by Doug Penner
Modified: 2010-10-18 20:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Doug Penner 2009-08-31 22:34:11 UTC 
If you turn on the screensaver (or lock the session) with a dual-head setup running gnome-shell, parts of the shell are still visible. It appears as though the screensaver is running inside a window (though I'm sure it's not).

This has some potentially serious security concerns if any of these parts of activate-able. Even if they are not, it allows people to see select parts of your desktop while you may not be looking.


Specs:
+gnome-shell: 2.26.3
+archlinux: fully updated
+gnome-shell: archlinux AUR
Comment 1 Dan Winship 2009-11-12 21:20:48 UTC 
does this still happen for you? i couldn't reproduce it last time i tried
Comment 2 Rui Matos 2009-11-12 23:46:06 UTC 
I've just ran a 'jhbuild build' and still see this bug on F11.

Only the shell panel is visible but most of its items are not activatable. The clock calendar drop down is activatable and visible "above" the screensaver though.

Also these messages appear on the terminal where the shell was launched:

JS LOG: pushModal: invocation of begin_modal failed

when one clicks on one of the non-activatable items like the Activities button.
Comment 3 Tobias Mueller 2010-04-19 10:46:18 UTC 
Reopening as per last comment.
Comment 4 William Jon McCann 2010-10-16 21:18:29 UTC 
Been quite a while, is this still an issue?
Comment 5 Doug Penner 2010-10-17 21:10:04 UTC 
Not that I know of. I haven't used gnome-shell for a little while and forgot to check the screensaver when I did.
Comment 6 Rui Matos 2010-10-18 19:27:10 UTC 
(In reply to comment #4)
> Been quite a while, is this still an issue?

Nope, not an issue anymore. Just tried it on the new overview-relayout branch and it is working fine when locking and unlocking the screen several times.
Comment 7 Milan Bouchet-Valat 2010-10-18 20:39:23 UTC 
Thanks for the feedback!