{num,caps,scroll} lock resets to off in Sway after switching from TTY

[Geo25rey]

Sway Version:
sway version v1.5-rc2-ea3ba203 (Jul 7 2020, branch 'master')

Debug Log:
https://gist.github.com/Geo25rey/5cb50e4ee29f022ab78bda0672081181

Configuration File:
DEFAULT

Description:

1. Open a program to type in.
2. Turn on Caps Lock and Num Lock
3. Confirm all letters are capitalized and numpad works
4. Switch to another TTY then switch back to Sway's TTY
5. Test letters and numpad again and see letters are lowercase and numpad outputs no numbers

Notes:

• I believe the issue is directly related to this comment from Sway resets keyboard layout to first after TTY switch #5456.

[RedSoxFan]

I believe the issue is directly related to this comment from #5456

Ya. Unfortunately, that does appear to be the case. I'd rather not store the entire xkb state in the input config, but I'm not sure what the alternative would be.

Related note: xkb_capslock and xkb_numlock are used, if set

[Geo25rey]

My initial thought is to "grab" (not sure of proper term) the keyboard so it would only be usable in sway, but that seems much worse than just saving the state of the keyboard.

I'm going to look into how systemd-logind handles it for ideas.

[Geo25rey]

@RedSoxFan I was looking into saving the xkb state temporarily when directly before a TTY switch then restoring it when focus is back on Sway's TTY, but I am struggling to find a way to poll for this event without root permission.

[emersion]

The input devices will be removed (and re-added) on a TTY switch.

[Geo25rey]

@emersion But the num lock and caps lock states are saved, regardless of the physical state of the keyboard (i. e. the num lock light being on or off) in TTYs.