FS#77729 - [systemd] Left and right mouse buttons swapped after an upgrade

Attached to Project: Arch Linux
Opened by Theodor R. (theor) - Saturday, 04 March 2023, 23:40 GMT
Last edited by Christian Hesse (eworm) - Monday, 06 March 2023, 12:48 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

I have Logitech Lift Vertical Ergonomic Mouse (the right-handed version). It's a wireless mouse. I use it with a USB dongle that comes with it. It worked perfectly fine until a recent systemd upgrade.

After upgrading packages systemd, systemd-libs, lib32-systemd and systemd-sysvcompat from 253-1 to 253.1-1 the left and right buttons suddenly switched places! Left button now acts like right button and right buttons acts like left.

I confirmed that with xev, it now reports left button as button 3 and right button as button 1.

Downgrading those packages back to 253-1 fixes the problem.

The problem only happens when using the USB dongle. If I switch the mouse to bluetooth mode, left and right buttons are back to normal.

Interesting thing is that the mouse starts acting like this immediately after upgrading, no reboot required. I suspect it happens at the hook "Reloading system bus configuration". But a reboot is still needed to get it back to normal after downgrading, which is strange.

Here's the device ID from lsusb:

Bus 002 Device 006: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver

Let me know if there's any other info I can provide.
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 06 March 2023, 12:48 GMT
Reason for closing:  Upstream
Additional comments about closing:  systemd-253.1-2
Comment by Toolybird (Toolybird) - Sunday, 05 March 2023, 05:58 GMT
*clearly* an upstream issue...and already reported:

https://github.com/systemd/systemd/issues/26671

Comment by Theodor R. (theor) - Sunday, 05 March 2023, 15:40 GMT
@Toolybird Thanks for linking the GitHub issue! Sorry I didn't do enough searching before reporting the bug here.

Loading...