<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: Switching between fullscreen and unfullscreen using F11 in google-chrome causes gnome-shell to hang" href="https://bugzilla.gnome.org/show_bug.cgi?id=762618#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: Switching between fullscreen and unfullscreen using F11 in google-chrome causes gnome-shell to hang" href="https://bugzilla.gnome.org/show_bug.cgi?id=762618">bug 762618</a> from <a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> Olivier Fourdan</a> <pre>Created <a href="attachment.cgi?id=322382" name="attach_322382" title="annotated log of events">attachment 322382</a> <a href="attachment.cgi?id=322382&action=edit" title="annotated log of events">[details]</a> annotated log of events So I added traces in gnome-shell when playing the fullscreen animations, in mutter when processing key events and in the xserver when processing xkb events, and reproduced the issue. It clearly show what is happening: 1. once the animation takes longer than the key repeast delay, the xserver starts emitting key press events by itself (auto-repeat) until a key release evenst is received 2. That triggers even more fullscreen transitions in the client 3. more fullscreen transitions cause more animations 4. killing the client doesn't immediately solves the problem because there is a lot of events queued 5. once things settle down, mutter processed the key release events at last</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>