swaylock: Sway crashes when unplugging keyboard, if any options are used #5205
Comments
|
This is also easily triggered with the virtual keyboard -- something like this works with the wayland backend, avoiding the need to disconnect anything and ruin one's primary session in the process. |
r-c-f
added a commit
to r-c-f/wlroots
that referenced
this issue
Apr 12, 2020
Check for a NULL keyboard_state.keyboard value in seat_client_create_keyboard() before trying to use it, as is done in other functions like seat_client_send_repeat_info(). Prevents a segfault in certain situations on keyboard removal, as seen in the sway issue (swaywm/sway#5205)
|
@r-c-f Just tested the wlroots PR and it looks to fix the issue on my end. |
emersion
pushed a commit
to swaywm/wlroots
that referenced
this issue
Apr 14, 2020
Check for a NULL keyboard_state.keyboard value in seat_client_create_keyboard() before trying to use it, as is done in other functions like seat_client_send_repeat_info(). Prevents a segfault in certain situations on keyboard removal, as seen in the sway issue. Closes: swaywm/sway#5205 Closes: #2073
|
I am having the same issue in 2024 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I unplug my keyboard when swaylock is awaiting input, sway crashes and it crashes severely enough that I need to reboot through SSH (or use sysrq). This only occurs if I configure the keyboard with any options like repeat_rate, xkb_options, etc. If I include an empty configuration like this:
then the crash doesn't occur. It's also okay if I don't specify the input at all. The debug log I've attached includes configurations for multiple detected input devices: "1155:20518:CATEX_TECH._75EC-S" and "1155:20518:CATEX_TECH._75EC-S_Keyboard" however specifying just one of these still triggers the bug. I also tested a different keyboard and can trigger the bug with that keyboard as well. In sum to reproduce:
Sway Version:
sway version 1.4-4d13cee5 (Apr 11 2020, branch 'HEAD')
Debug Log: Debug log Gist
Configuration File: Config gist
Stack Trace, if sway crashes:
Attaching to sway and/or swaylock appears to prevent keyboard input completely (or is extremely slow). Will try again later if needed. I don't have coredumpctl as an option since I don't use systemd.
The text was updated successfully, but these errors were encountered: