Connecting to a wireless mouse breaks desktop environment

grzmot1337 · 2024-01-16 08:51:31

Hi, yesterday I encountered some strange problem with my mouse. I've been using my pc for around couple of hours (playing games, programming), nothing special. While programming i noticed that using the scroll wheel to open sites in a new tab stopped to work, but I thought whatever it will be probably back to normal after reboot. After some time, my scroll stopped to work entirely in sublime editor, actually mouse stopped to work in sublime editor. There was something wrong. Moving my mouse was perfectly smooth as normal but the windows stopped to react to my mouse movement? I couldn't click on most things, everything stopped highlighting when my mouse was over it. Also, when switching to a different window on desktop (Alt + Tab) the window seemed to be highlighted as the primary one, but my keyboard was still typing on the previous one? And it wasn't consistent at all, it could stop for some couple of seconds to normal and then break again.

First thing I did was reboot - nothing changed, so I thought that I may broke something with a package update (even though I haven't update anything in previous session), so I removed unused packages and reinstalled all the other ones.
Okay, I guess it was better now? Desktop was more functional but some things like using my scroll button to open sites in a new tab still wasn't. After that i rebooted again, just like after any other major update... it was broken again.
I thought I will have to reinstall whole system, but I thought that there may be problem with my mouse so i connected to my girlfriend laptop (Windows 11) and it wasn't working too, I thought great I just need to buy a new mouse. After couple of minutes, she said she can't use her touchpad anymore even though I disconnected the mouse so everything should be back to normal right? I told her to reboot, and the touchpad worked again.

Today I logged onto my work laptop (Windows 10) and connected with my mouse to it - also broken. I forgot to say that some other mouse works perfectly on everything. I noticed that it took maybe 3-4 minutes on my work laptop to be broken after connecting to my mouse. So, it seems that my mouse breaks every device (Arch, Windows10, Windows 11).

Mouse model: Steelseries Rival 3 Wireless

seth · 2024-01-16 09:15:12

Is there a question or are you blogging your live?

I read through two long paragraphs of uninspired anecdotes to get to the point:

my mouse breaks every device (Arch, Windows10, Windows 11).
Mouse model: Steelseries Rival 3 Wireless

It might generate spurious input (you can check that w/ "evtest" or libinput "debug-events") or completely trash the USB stack (though that would affect more than other input devices, eg. usb keys)

If you just wanted to report about your life: get a blog.

grzmot1337 · 2024-01-16 21:41:51

Both "evtest" and "debug-events" showed no strange behavior. I also compared the output to the one with working mouse - no difference.

seth · 2024-01-16 21:44:14

Do usb keys still work (are they detected at all, can you mount them)?
Have you btw. tried to swap the batteries on the mouse?

grzmot1337 · 2024-01-25 13:53:24

Usb keys working correctly, swapping batteries did nothing.

seth · 2024-01-25 14:14:17

Keep "dmesg -w" running in some terminal and see whether you get any errors there when the mouse acts up, wrt

Both "evtest" and "debug-events" showed no strange behavior.

This is when the mouse trashed the input?
What does evtest actually do print for the device - notably in reponse to actions (are presses and releases correctly reported?)

grzmot1337 · 2024-02-04 15:17:31

Okay, I tried using rival 3 again after some time - it worked perfectly for around 2 hours.
I also discovered that in both evtest and debug-events there is no output when it comes to clicking scroll wheel, though scrolling is recorded.
Here's the dmesg -w output:

[17521.942491] usb 1-4: New USB device found, idVendor=1038, idProduct=1830, bcdDevice= 1.04
[17521.942498] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[17521.942501] usb 1-4: Product: SteelSeries Rival 3 Wireless
[17521.942503] usb 1-4: Manufacturer: SteelSeries
[17521.972597] input: SteelSeries SteelSeries Rival 3 Wireless as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-4/1-4:1.0/0003:1038:1830.003B/input/input62
[17521.972698] hid-generic 0003:1038:1830.003B: input,hidraw6: USB HID v1.11 Mouse [SteelSeries SteelSeries Rival 3 Wireless] on usb-0000:02:00.0-4/input0
[17521.979891] input: SteelSeries SteelSeries Rival 3 Wireless Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-4/1-4:1.1/0003:1038:1830.003C/input/input63
[17522.034767] hid-generic 0003:1038:1830.003C: input,hidraw7: USB HID v1.11 Keyboard [SteelSeries SteelSeries Rival 3 Wireless] on usb-0000:02:00.0-4/input1
[17522.039735] hid-generic 0003:1038:1830.003D: hiddev98,hidraw8: USB HID v1.11 Device [SteelSeries SteelSeries Rival 3 Wireless] on usb-0000:02:00.0-4/input2
[17522.045658] hid-generic 0003:1038:1830.003E: hiddev99,hidraw9: USB HID v1.11 Device [SteelSeries SteelSeries Rival 3 Wireless] on usb-0000:02:00.0-4/input3
[17579.365434] usb 1-4: USB disconnect, device number 17

seth · 2024-02-04 15:28:41

The dmesg only shows that device disconnected after ~1 minute?
Did you at any point still experience the original problems or did it just work for 2h and then you stopped trying?

no output when it comes to clicking scroll wheel, though scrolling is recorded

Is only one button (the scrollwheel) affected? Permanently? Could it be broken (or stuck)?

grzmot1337 · 2024-02-05 12:45:11

The USB disconnect info is after I unplugged the usb receiver so that's fine.
It stopped working after 2 hours (original problems), today I tried with my laptop - it worked for about 3 minutes.
I don't think scroll wheel is stuck or something, seems to be "mechanically" normal.

c00ter · 2024-02-05 13:22:05

Have you tried using a different mouse? It sounds from your description that this mouse may be either losing signal (where is the receiver located?) or just plain broken. And batteries?

Last edited by c00ter (2024-02-05 13:23:02)

seth · 2024-02-05 14:34:35

It stopped working after 2 hours (original problems), today I tried with my laptop - it worked for about 3 minutes.

Then that's not in the dmesg tail which only shows the mouse being connected and then lost after 60s

W/ the random and delayed behavior it could easily be the mouse responding badly to https://wiki.archlinux.org/title/Power_ … utosuspend - adding "usbcore.autosuspend=-1" to the kernel parameters will globally disable it.
Be aware that userspace powermanagers like TLP can and will override that value and you'll have to configure the behavior there (as well)

Arch Linux

#1 2024-01-16 08:51:31

Connecting to a wireless mouse breaks desktop environment

#2 2024-01-16 09:15:12

Re: Connecting to a wireless mouse breaks desktop environment

#3 2024-01-16 21:41:51

Re: Connecting to a wireless mouse breaks desktop environment

#4 2024-01-16 21:44:14

Re: Connecting to a wireless mouse breaks desktop environment

#5 2024-01-25 13:53:24

Re: Connecting to a wireless mouse breaks desktop environment

#6 2024-01-25 14:14:17

Re: Connecting to a wireless mouse breaks desktop environment

#7 2024-02-04 15:17:31

Re: Connecting to a wireless mouse breaks desktop environment

#8 2024-02-04 15:28:41

Re: Connecting to a wireless mouse breaks desktop environment

#9 2024-02-05 12:45:11

Re: Connecting to a wireless mouse breaks desktop environment

#10 2024-02-05 13:22:05

Re: Connecting to a wireless mouse breaks desktop environment

#11 2024-02-05 14:34:35

Re: Connecting to a wireless mouse breaks desktop environment

Board footer