systemd has nothing at all to do with what happens on the keypresses.
udev only adjusts the kernel's keymaps during boot. But at runtime, the
keypresses are handled by the kernel, sent through /dev/input/* as evdev
events, and read by *-settings-daemon or other programs. So tentatively
assigning to
I wonder if this is really systemd related, we know that unity-settings-
daemon reveal some similar issues (though, most of the time, they are
all lost and even restarting it isn't succifient as it misses some env
variable to leak in the session).
So, let's figure out if it's systemd related first
2 matches
Mail list logo
