diff options
| author |  Brian Ashworth <bosrsf04@gmail.com> | 2020-05-18 17:52:13 -0400 |
|---|---|---|
| committer |  Tudor Brindus <me@tbrindus.ca> | 2020-05-19 15:42:32 -0400 |
| commit | 5c32a4845354e59133b1d213928d8cee1b8691bd (patch) | |
| tree | 2b1aded3991d25558a91f8ec3b4b24dbd36e6ae4 /sway/sway.5.scd | |
| parent | bash completion: swaymsg accepts --version, not --verbose (diff) | |
| download | sway-5c32a4845354e59133b1d213928d8cee1b8691bd.tar.gz sway-5c32a4845354e59133b1d213928d8cee1b8691bd.tar.zst sway-5c32a4845354e59133b1d213928d8cee1b8691bd.zip | |
input: fix reloading crash due to keyboard group configuring
Keyboard group keyboards should not call sway_keyboard_configure. They
do not have an input config and they derive their state from the
keyboards within the group.
For some reason, I got sway_keyboard_configure and
seat_configure_keyboard mixed up and thought seat_reset_device called
the latter.
Calling sway_keyboard_configure with a keyboard group's keyboard is not
supported and can cause issues. If any clients are listening to the ipc
input event, a sigsegv will occur due to not every property - such as
identifier - being wired up for keyboard group keyboard's.
This also adds an assertion to sway_keyboard_configure to ensure that
this does not occur in the future and any instances are quickly caught.
Diffstat (limited to 'sway/sway.5.scd')
0 files changed, 0 insertions, 0 deletions