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 719778 - After multiple rapid presses on overlay-key signal stops emitting
After multiple rapid presses on overlay-key signal stops emitting
Status: RESOLVED DUPLICATE of bug 666101
Product: mutter
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-12-03 14:51 UTC by Aleksey Yermakov
Modified: 2014-03-06 13:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aleksey Yermakov 2013-12-03 14:51:19 UTC 
After multiple rapid presses on overlay-key (Super key), overlay-key signal stops emitting.

How to reproduce:
1. Restart gnome-shell to catch output to terminal: gnome-shell --replace
1. Launch looking glass: <Alt+F2> -> lg -> <Enter>
2. Execute this in lg: global.display.connect("overlay-key", function() { print("OVERLAY-KEY EMITTED"); });
3. Close lg: <Esc>
4. Start rapidly pressing overlay-key and check output in terminal
5. After few presses overlay-key stops emitting
6. You can refocus terminal window to reset this state
Comment 1 Owen Taylor 2014-03-06 01:13:44 UTC 
I can't reproduce this either with mutter 3.10.3 or the current 3.11.x development branch. 
 
 Does it matter just how rapidly you are pressing the overlay-key?
  (Is your machine particularly slow or fast?)
 Does it ever not happen for you?
 Do you have any extensions installed? 
 Do any errors get printed to the terminal when the overlay key stops working?

Thanks!
Comment 2 Jasper St. Pierre (not reading bugmail) 2014-03-06 01:38:33 UTC 
Probably a duplicate of bug #666101, where this can trigger if you leave the overview with the overlay key pressed.

The issue being of course that exiting the compositor modal calls XIUngrabDevice, trying to drop our compositor modal, but also drops our Sync grab for the overlay key state machine.
Comment 3 Owen Taylor 2014-03-06 02:00:27 UTC 
Aleksey - what version of Mutter are you using?
Comment 4 Aleksey Yermakov 2014-03-06 06:49:09 UTC 
(In reply to comment #1)
>  Does it matter just how rapidly you are pressing the overlay-key?
>   (Is your machine particularly slow or fast?)

Yes, I press really rapidly. It's much easier to reproduce on VirtualBox without 3d acceleration - on very "slow" system, but also reproduces on hardware installed system.

>  Does it ever not happen for you?

Happens all the time.

>  Do you have any extensions installed?

Disabled all extensions - still happens.

>  Do any errors get printed to the terminal when the overlay key stops working?

Nope, no errors at all.


(In reply to comment #3)
> Aleksey - what version of Mutter are you using?

I'm using mutter-3.8.4.
Comment 5 Aleksey Yermakov 2014-03-06 06:57:25 UTC 
Just checked on Debian 7.2 with mutter-3.4.1 - reproduced.
Comment 6 Owen Taylor 2014-03-06 13:55:30 UTC 
(In reply to comment #4)

> (In reply to comment #3)
> > Aleksey - what version of Mutter are you using?
> 
> I'm using mutter-3.8.4.

OK, sounds like this is likely the bug Jasper mentioned, which was fixed in GNOME 3.10.

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