[Wayland-bugs] [Bug 762618] wayland: Switching between fullscreen and unfullscreen using F11 in google-chrome causes gnome-shell to hang

mutter (GNOME Bugzilla) bugzilla at gnome.org
Wed Feb 24 17:23:16 UTC 2016


https://bugzilla.gnome.org/show_bug.cgi?id=762618

--- Comment #4 from Olivier Fourdan <ofourdan at redhat.com> ---
So here is what I think is happening:

1. Press F11 to switch to fullscreen
2. Press F11 to switch back to normal
3. The HW is pretty slow, shell_util_get_content_for_window_actor() takes a
noticeable time to complete
4. the Key release is lost/eaten somehow between gnome-shell and Xwayland
5. Xwayland doesn't get the Key release and therefore performs auto-repeat
6. Xwayland generates Key press/release events sent to the application
7. the application changes its state to/from fullscreen
8. gnome-shell is too busy dealing with the state changes that queue up (as
shell_util_get_content_for_window_actor takes a lot of time) and doesn't
process input events (the pointer is stuck as well)
9. we're doomed, XWayland keeps sending press/release events faster than
gnome-shell can deal wit hteh consequences of the app changing state ...

=> The question is why don't Xwayland get the Key release in the first place,
that's what is causing the key repeat.

(hint, disabling key auto-repeat avoids the issue)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20160224/eecd4d58/attachment.html>


More information about the wayland-bugs mailing list