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

[mutter (GNOME Bugzilla)]

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

--- Comment #2 from Olivier Fourdan <ofourdan at redhat.com> ---
Ah right, my bad, obviously X11 aps don't use wayland stuff, they change their
state using the EWMH "protocol" (set_net_wm_state() in mutter)

Now what's interesting, because listening to events on the root window, it
looks like the keypress/keyrelease event is repeated continuously:

KeyRelease event, serial 23, synthetic NO, window 0x263,
    root 0x263, subw 0x200122, time 2969205, (383,484), root:(383,484),
    state 0x0, keycode 95 (keysym 0xffc8, F11), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 23, synthetic NO, window 0x263,
    root 0x263, subw 0x200122, time 2969205, (383,484), root:(383,484),
    state 0x0, keycode 95 (keysym 0xffc8, F11), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 23, synthetic NO, window 0x263,
    root 0x263, subw 0x200122, time 2969235, (383,484), root:(383,484),
    state 0x0, keycode 95 (keysym 0xffc8, F11), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 23, synthetic NO, window 0x263,
    root 0x263, subw 0x200122, time 2969235, (383,484), root:(383,484),
    state 0x0, keycode 95 (keysym 0xffc8, F11), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

-- 
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/7a7401b6/attachment.html>