keyboards are all put in their own separate groups

[ashkitten]

• Sway Version: sway version 1.5-f5ca4c26 (branch 'master')

• Debug Log: https://gist.github.com/ashkitten/ccdbe290a041ad3fb5083ddd23050b73

• Configuration File: reproducible with default configuration

• Description: keyboard devices are all in separate keyboard groups, causing modifier presses on one to not affect the state of others. it used to group them properly, but sometime recently stopped working.

[emersion]

Can you provide the output of sudo libinput list-devices?

[ashkitten]

sure, https://gist.github.com/ashkitten/68aa0159eb1b18e6e092fedbf9bee3c4

[emersion]

Does this list your keyboards groupped the way you'd expect? If not, report a bug to libinput.

[ashkitten]

the output of libinput list-devices looks different from the groups that sway shows on startup (adding each keyboard device to a separate group)

additionally though, the behavior i've been relying on in sway is that the keyboard and mouse were grouped together so i could use modifiers on one to affect the other. without this, i can't copy text in the terminal using my mouse while holding shift on my keyboard.

the documentation for sway-input says that all keyboards in a seat are grouped by their keymap and repeat info when using keyboard_grouping smart which should mean that my mouse and keyboard are grouped together. if this is not the case, the documentation should be clarified and a new keyboard_grouping option should be added for the wanted behavior.