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 684320 - Pressing ESC a ton of times on the Lock Screen breaks the Lock Screen.
Pressing ESC a ton of times on the Lock Screen breaks the Lock Screen.
Status: RESOLVED DUPLICATE of bug 684028
Product: gnome-shell
Classification: Core
Component: lock-screen
3.5.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-09-18 19:37 UTC by Tom Wijsman
Modified: 2012-09-18 20:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tom Wijsman 2012-09-18 19:37:03 UTC 
Just keep pressing the ESC button in quick succession.

This time, I'm starting properly with gdm so it's not a duplicate of bug 683757 as bug 683755 got resolved, I'm also no longer using the patch from bug 683060 as that bug doesn't occur to me anymore as bug 683755 got resolved...

The difference here is that pressing the ESC once normally works to hide and show the curtain, but there still seems to be a bug when pressing it in quick suggestion (which means that hitting it twice might break the lock screen altogether).
Comment 1 Giovanni Campagna 2012-09-18 19:58:49 UTC 
What version are you using? If it's less than 3.5.91-97-g107f5de, it's a duplicate of bug 684028.
In any case, I got GDM to crash by very quickly pressing ESC.

I have backtraces too, but before I reassign and attach them, I'd like to make sure it's not a shell bug.
Comment 2 Tom Wijsman 2012-09-18 20:11:46 UTC 
Great to hear this has been fixed upstream. I'm using the released version of 3.5.91; so, it's most likely you are having a more recent version than me. If you can't replicate this on the version you are on, then you can leave this bug closed.

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