[Wayland-bugs] [Bug 782534] New: GdkKeymap modifier state doesn't seem work under wayland

[gtk+ (GNOME Bugzilla)]

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

            Bug ID: 782534
           Summary: GdkKeymap modifier state doesn't seem work under
                    wayland
    Classification: Platform
           Product: gtk+
           Version: 3.22.x
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: Backend: Wayland
          Assignee: gtk-bugs at gtk.org
          Reporter: jonathon at quotidian.org
        QA Contact: gtk-bugs at gtk.org
                CC: rob at robster.org.uk, wayland-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 351669
  --> https://bugzilla.gnome.org/attachment.cgi?id=351669&action=edit
test case

When running Gtk+ applications under wayland, it seems that the
gdk_keymap_get_modifier_state() always returns 0 for the default keymap, and
the 'state-changed' signal does not get emitted when (for example) the caps
lock is depressed. When running under x11, the signal *does* get emitted. 

Minimal test case attached. Compile and run the test case executable and press
various modifiers (caps lock, shift, ctrl, num lock, etc). 

When the test case is run under Wayland, I get an initial signal immediately
after the executable starts and the debug output indicates that the modifier
state is 0 regardless of whether any modifiers are active.

When the test case is run under X11, a new message is printed to the terminal
every time a modifier is activated or de-activated.

-- 
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/20170511/92b99faf/attachment-0001.html>