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 651874 - Suspend lock order faulty
Suspend lock order faulty
Status: RESOLVED DUPLICATE of bug 655924
Product: gnome-shell
Classification: Core
Component: general
3.0.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 649691 652324 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-06-04 20:47 UTC by xenhu134
Modified: 2011-08-25 20:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description xenhu134 2011-06-04 20:47:48 UTC 
Select "Suspend" from menu. Computer suspends properly. Wake the computer up. I can see brief flash of the display, full desktop with all contents, before the display gets locked up asking password to unlock.

The order is probably wrong. The desktop should be locked before actual suspend. Or then the display should be locked up somehow before drawing it full when coming back from suspend.

Unfortunately I see this as a security breach.
Comment 1 Rui Matos 2011-06-05 11:22:56 UTC 
*** Bug 649691 has been marked as a duplicate of this bug. ***
Comment 2 Rui Matos 2011-06-05 12:38:33 UTC 
Interestingly, I can reproduce this with the nouveau driver but can't with the nvidia blob on the same hardware.
Comment 3 xenhu134 2011-06-05 16:02:23 UTC 
I am using the open source intel driver, with HD2000 (lower end i3 integrated adapter). The flash takes some 0.2 seconds, which is enough to get a glimpse of all of the contents before the screen locks. I would manage to get a screen capture in that time if I put effort into it.
Comment 4 Florian Müllner 2011-06-10 20:32:55 UTC 
*** Bug 652324 has been marked as a duplicate of this bug. ***
Comment 5 Matthias Clasen 2011-08-25 20:49:36 UTC 

*** This bug has been marked as a duplicate of bug 646750 ***
Comment 6 Matthias Clasen 2011-08-25 20:55:50 UTC 

*** This bug has been marked as a duplicate of bug 655924 ***