Closed jvasile closed 1 month ago
Upon reflection, I think this might not be a keyd issue. The reason keyd isn't grabbing keystrokes might be because another process is grabbing them. And that wouldn't be keyd's fault. A race condition would also explain the intermittent nature of the failure. I need to eliminate that possibility. When I am next in front of that computer, I will do that. In the meantime, I think this should be closed.
If I run keyd for a while, sometimes it starts eating keystrokes instead of passing them on. If I ctrl-alt-f2, then ctrl-alt-f1, I go to a vterm and then back to my x session. And then maybe it works.
But also sometimes that doesn't help. And so I restart keyd and... it doesn't come back properly. It just will not attach to keyboards. In
keyd --monitor
see a message saying it's attaching to my keyboard. And I see CONFIG: parsing of my files with no errors reported. And monitor shows my keypresses going by, but nothing more happens. Restarting keyd doesn't help.This is enough of a problem that it happens every few days. Rebooting clears it.
I don't know enough about the device interruption dance keyd is doing to really dig in and debug. And it's an intermittent bug. Usually all is well and restarting keyd is just fine.
Thank you!