catman has quit [Remote host closed the connection]
waleee has quit [Ping timeout: 260 seconds]
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 255 seconds]
leopoldek has quit [Remote host closed the connection]
notzmv has quit [Remote host closed the connection]
notzmv has joined #river
lillian has joined #river
<lillian>
hello, i updated my system this morning and my terminal no longer accepts text input properly. river (not the terminal, which is why i'm asking here) is spamming xkbcomp unsupported maximum keycode errors. any idea what the issue might be?
<lillian>
terminals kitty and wezterm don't work, but foot does
<lillian>
looks like this doesn't happen if i run kitty in xwayland
lillian has quit [Ping timeout: 260 seconds]
lillian has joined #river
<novakane>
lillian: unsupported maximum keycode is harmless, so that's probably not the problem
<novakane>
kitty and wezterm aren't exactly the best well behaving terminals under wayland so could be clients bugs
<novakane>
a river debug log could help maybe though
<lillian>
novakane, i traced it back to fcitx5 and chromium, there is a spam of `removed input device: keyboard-0-0-wlr_virtual_keyboard_v1` and `new input device: keyboard-0-0-wlr_virtual_keyboard_v1` in the debug logs
<lillian>
well fcitx5 and any app that actually works with it
<lillian>
hm my page up/down keys don't work anymore
<novakane>
seems like there is some problems with fctix last version
angry_vincent has quit [Ping timeout: 255 seconds]
<yongxiang>
Thanks for that, I thought the scaling configuration was part of the river.
<yongxiang>
I want wayland scaled to 2x and xwayland off zoom. How should I configure? I'm not sure if this should belong to the river or the external output configuration?