Timeline for xmodmap lost after sleep
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2024 at 21:48 | comment | added | U. Windl | I think the actual problem is that "reconnecting the keyboard" happens at kernel level (say "root"), and it's hard to trigger a user-level action (e.g. via udev) from that: Imagine multiple users each have a different setting in their home directory: Which user to pick? Still, you could try a system-wide setting. Maybe see superuser.com/q/1576107 | |
| Dec 2, 2020 at 19:03 | history | bounty awarded | CommunityBot | ||
| Dec 2, 2020 at 4:02 | comment | added | Cem Kalyoncu | Could you provide some information about how to add a script to hotplug processing? | |
| Nov 25, 2020 at 11:54 | comment | added | Cem Kalyoncu | Disconnecting and reconnecting any input device causes the reset, which is something I hate too. It seems the real solution here is to modify keyboard layout. | |
| Nov 24, 2020 at 17:41 | history | answered | Simon Richter | CC BY-SA 4.0 |