Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

systemd 238 (+ patch) breaks my mouse #8579

Closed
Baughn opened this issue Mar 26, 2018 · 5 comments

Comments

@Baughn
Copy link

commented Mar 26, 2018

Submission type

  • Bug report

systemd version the issue has been seen with

238.0

238.0 + #8493

Used distribution

NixOS 18.03pre-git (Impala)

In case of bug report: Expected behaviour you didn't see

All mouse buttons should work

In case of bug report: Unexpected behaviour you saw

For 238.0: Mouse does not work at all.
For 238.0 + patch: Some buttons no longer work.

In case of bug report: Steps to reproduce the problem

  • Purchase a MadCatz MMO 7 mouse, or (likely) any other mouse with >16 buttons.
  • Run xev to confirm that some buttons don't function.

Further information

The original bug is #8460, which was patched by #8493. Unfortunately, this patch causes the system to ignore any buttons beyond the first sixteen.

The mouse worked fine with systemd 237, so this is a regression.

@poettering

This comment has been minimized.

Copy link
Member

commented Mar 26, 2018

/cc @whot

@whot

This comment has been minimized.

Copy link
Contributor

commented Apr 2, 2018

sorry, was on holidays.

can you confirm that sudo evemu-record shows events for all buttons? If not -> kernel issue
what driver are you using? libinput or evdev? or wayland (in which case it's libinput)

The reason I'm asking: the ID_INPUT tags have no effect on button reporting, they literally only say "this is a mouse" or "this is a touchpad" but don't do anything about the event processing itself. So the only two options I can see are either the kernel got updated together with systemd and that broke things or libinput is confused about something now.

@tr37ion

This comment has been minimized.

Copy link

commented Apr 12, 2018

Applying ae5fd19 did fix the mouse issue #8460 and using sudo evemu-record shows all buttons are working. While xev | egrep ^Button only recognizes some of the buttons.

With KDE Plasma's "Input Device/Joystick" settings all buttons are working and even the special ModeSet button (20) switches the pressed state of buttons 1,2 and 22. Which is well, because this makes it possible to apply a complete new subset of button assignments depending on which of those three buttons has pressed state.

@poettering

This comment has been minimized.

Copy link
Member

commented Apr 17, 2018

So what does this mean? Can we close this bug?

@whot

This comment has been minimized.

Copy link
Contributor

commented May 2, 2018

Taking the silence as a 'yes'

@whot whot closed this May 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
You can’t perform that action at this time.