https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #23 from joey.joey...@gmail.com --- The systemd github had just replied an hour ago. They say it's most likely not their bug and more likely due to how KDE or libinput handles the configuration once "udevadm trigger -s input" is run. However, I doubt if this is a libinput issue, since I ran the same commands on Fedora GNOME 31 (which also uses libinput) and nothing happened. Could it be the way KDE handles its touchpad management/configuration? -- You are receiving this mail because: You are watching all bug changes.
