wtype makes input unusable

[zoriya]

wtype (a binary that inputs keys through the virtual-keyboard protocol) works as it should but once it exits (and closes the virtual keyboard), the selected app stops receiving input events from your keyboard.

Reproduction

• run wtype -k p in a shell
• observe that p got written (as it should)
• observe that your keyboard does not input anymore until you unfocus the app (niri keybinds still work)

System Information

• niri version: niri 25.05.1 (Nixpkgs)

• Distro: nixos

• GPU: /

• CPU: /

[brianmercer]

I just switched from sway and have run into this behavior.

I have a tablet and I use wvkbd as my on screen keyboard. I use wtype to send a return to pam before I can use my fingerprint scanner to unlock swaylock after suspend. But those details don't matter for this issue.

Same as above, using wtype disables wvkbd for any open applications. Applications started after using wtype work fine.

[YaLTeR]

@Bot-wxt1221 do you think this (and the linked issues around it) could be related to the combined virtual keyboard keymap that you have a PR in Smithay for?

[Bot-wxt1221]

Err. The problem related to keymap won't disappear when switching app. But that could be different in different ime or other thing.

UPD: completely unrelated. I can reduce the problem with patch.

[Bot-wxt1221]

@zoriya Could you post WAYLAND_DEBUG=1

[brianmercer]

log.txt

[zoriya]

thanks for sending this in my stead, im in vacation and won't be back on my computer to send logs before ~1.5 weeks

[Bot-wxt1221]

I find that wtype set time as 0 in zwp_virtual_keyboard_v1::key

But I still wonder how wayland process time why would it be 0?

[Bot-wxt1221]

Oh I got the problem. This is still related to keymap. This is because the old keymap for real keyboard wasn't set after virtual input. This is solved in #2246

[Bot-wxt1221]

This should work until we have Smithay/smithay#1903 or further impl.