fix: load uinput in Arch hook - #126
Merged
Merged
Conversation
mmaher88
approved these changes
Jul 28, 2026
mmaher88
left a comment
Owner
There was a problem hiding this comment.
Verified: brings the Arch hook in line with the deb postinst and RPM spec, which already narrow udevadm trigger to hidraw/misc instead of re-triggering every device. The modprobe uinput is the right call — without the module loaded there's no /dev/uinput node for udev to tag with uaccess. The || true guards also mean a failing hook can't abort the install. Thanks!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What happened
On my Manjaro KDE Wayland system, Logitune detected the mouse and received
button events correctly, but remapped button actions did nothing.
The log showed that hidraw access was working:
But uinput initialization failed:
Root cause
In my case,
/dev/uinputexisted, but the actual uinput kernel device wasnot loaded or registered:
Because of that, reloading and triggering udev rules was not enough. The rule
with
TAG+="uaccess"had no livemisc/uinputdevice to apply to.Fix
This patch loads the uinput kernel module in the Arch install hook before
reloading and triggering udev rules.
It then triggers:
misc/uinput, souaccesscan be applied to/dev/uinputhidraw, so Logitech device permissions are refreshed as beforeAfter manually running
modprobe uinputand reloading udev rules on my system,Logitune stopped failing uinput init, and button remaps started working.