Arrows not working on Wayland

[somepaulo]

In my case (Arch/Gnome latest) the arrow keys don't move the ruler (with or without Ctrl).
All other shortcuts seem to work.

[epilys]

I pushed a commit that adds more arrow symbols for gtk accelerators, could you try to see if it works now?

[somepaulo]

Nope, still not moving.
The system beeps are gone though.

[epilys]

Are you using X11 or Wayland? If the former, could you tell me what keycodes show up when you press the arrow keys with xev? https://archlinux.org/packages/extra/x86_64/xorg-xev/

[somepaulo]

I'm on Wayland.
This is a Lenovo laptop with a pretty straight-forward setup, nothing fancy, not much tweaking, two language layouts, standard vanilla Gnome with a few extensions, that's about it.

The keycodes are 111 for up, 116 for down, 113 for left and 114 for right.
Here's what xev detects when I press up, down, left, right:

KeyPress event, serial 38, synthetic NO, window 0x1800001,
    root 0x496, subw 0x1800002, time 80926042, (36,33), root:(36,102),
    state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x1800001,
    root 0x496, subw 0x1800002, time 80926141, (36,33), root:(36,102),
    state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x1800001,
    root 0x496, subw 0x1800002, time 80926770, (36,33), root:(36,102),
    state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x1800001,
    root 0x496, subw 0x1800002, time 80926880, (36,33), root:(36,102),
    state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x1800001,
    root 0x496, subw 0x1800002, time 80927529, (36,33), root:(36,102),
    state 0x0, keycode 113 (keysym 0xff51, Left), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x1800001,
    root 0x496, subw 0x1800002, time 80927643, (36,33), root:(36,102),
    state 0x0, keycode 113 (keysym 0xff51, Left), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x1800001,
    root 0x496, subw 0x1800002, time 80928296, (36,33), root:(36,102),
    state 0x0, keycode 114 (keysym 0xff53, Right), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x1800001,
    root 0x496, subw 0x1800002, time 80928411, (36,33), root:(36,102),
    state 0x0, keycode 114 (keysym 0xff53, Right), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

[epilys]

I wonder if this is wayland related (i.e. the bug is in gdk library, not on the rlr code) keysym seem correct at least 🤔

[somepaulo]

I wonder if this is wayland related

It definitely is. Arrows work fine on Xorg, but not on Wayland.
Kruler somehow works on either server. Maybe there's a clue in their implementation?

It's weird that all the other keypresses are interpreted by the app correctly.