I have a Logitech wireless USB mouse that I can’t get to work on either of two Linux laptops, but previously worked on one of them and currently works on a Windows laptop.
The laptop it used to work on is running Artix (systemd-less Arch) with Sway. Current state of affairs is that I see a device created for it: /dev/hidraw1 (the touchpad is hidraw0 here), and swaymsg -t get_inputs, with or without the mouse connected, shows:
Input device: PS/2 Generic Mouse
Type: Mouse
Identifier: 2:1:PS/2_Generic_Mouse
Product ID: 1
Vendor ID: 2
Libinput Send Events: enabled
Input device: PNP0C50:00 2808:0101 Mouse
Type: Mouse
Identifier: 10248:257:PNP0C50:00_2808:0101_Mouse
Product ID: 257
Vendor ID: 10248
Libinput Send Events: enabled
and no inputs are received. wev also shows nothing.
The other laptop is running Manjaro with the default XFCE desktop. Here is dmesg output from it being connected:
[24700.621257] usb 1-2: new full-speed USB device number 7 using xhci_hcd
[24700.768351] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=24.01
[24700.768359] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[24700.768363] usb 1-2: Product: USB Receiver
[24700.768366] usb 1-2: Manufacturer: Logitech
[24700.785403] logitech-djreceiver 0003:046D:C52B.000B: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-2/input2
[24700.912748] logitech-hidpp-device 0003:046D:101B.000C: hidraw1: USB HID v1.11 Device [Logitech Wireless Device PID:101b] on usb-0000:00:14.0-2/input2:1
[24705.438614] audit: type=1101 audit(1637459838.096:311): pid=15583 uid=1000 auid=1000 ses=6 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="raven" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[24705.438875] audit: type=1110 audit(1637459838.096:312): pid=15583 uid=1000 auid=1000 ses=6 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[24705.441881] audit: type=1105 audit(1637459838.099:313): pid=15583 uid=1000 auid=1000 ses=6 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[24705.462551] audit: type=1106 audit(1637459838.119:314): pid=15583 uid=1000 auid=1000 ses=6 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[24705.462770] audit: type=1104 audit(1637459838.119:315): pid=15583 uid=1000 auid=1000 ses=6 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[24710.941691] audit: type=1101 audit(1637459843.599:316): pid=15611 uid=1000 auid=1000 ses=6 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="raven" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[24710.942373] audit: type=1110 audit(1637459843.599:317): pid=15611 uid=1000 auid=1000 ses=6 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[24710.949104] audit: type=1105 audit(1637459843.606:318): pid=15611 uid=1000 auid=1000 ses=6 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
But the Xorg log and xev show nothing, and no inputs are received.
Why not report it over to the Artix team, or if you did, why not link that post in here instead. With this information, no one can help you because you need the exact same setup and device to reproduce it.
Software wise I had multiple ideas but without anything further or a test device it is just guessing on my end.
I didn’t report it to the Artix, Manjaro or Arch teams because I don’t believe it’s a bug in any of those systems, and if I did report it to them, they would be in the same position as you. I realize it’s not likely that anyone else can reproduce the symptoms, rather I’m hoping that someone who knows more about mice in Linux in general will suggest other things I could try. You said you had multiple ideas, so can you please tell me what they are? I’m not asking you to solve my problem, I’d just like some troubleshooting pointers.
To come to a more productive level here, it would be very important to tell us what you actually already tried, I mean not only the actual output from what we cannot reproduce. I mean, steps you tried to come to a conclusion that this is maybe Os related issue.
- Other keyboards and mouses are working on the same port… maybe try this first.
- If other distros working and you ensured your hardware is not defect, then report this to the maintainers, and wait for their response.
- My ideas, or most of them are written down in this thread.
- My first guess is what I would try is to rule our power issues with the mouse itself or the driver. Then I would check for misconfiguration of XFCE and/or X.Org.
If that still brings you no step further, then you simply need to report it in the official forum.