It has been about 3 days since I got this bug in my pc. I don’t know if it’s the hardware or software, maybe both.
No matter if i am playing games, watching youtube, etc, my mouse hangs almost every 3 seconds or randomly. This happens anytime while doing anything. Even if i have no apps open.
Some details for diagnostic:
What speaks against trying another mouse? If you don’t want to buy a cheap 5€ mouse for testing purposes, how about asking a friend or colleague to borrow you one?
I’ll describe my experience. I don’t know whether it is relevant.
What you describe did happen to me with a wireless mouse. This was on my desktop computer. I moved the wireless dongle from the back of the computer to the front, and the problem went away. I think there was too much metal between the dongle and the mouse that interfered with the wireless communication.
First, I see that, this is your first post in these Forums –
So, now – can you please install the “inxi” package from the Tumbleweed repositories – it should be present in the main repository.
Then, can you please post the output of –
> inxi --admin -xxx --usb
For the case of your Mouse, in the output you should see some lines something like this:
Device-2: 1-10:5 info: Logitech M-U0007 [Corded Mouse M500] type: Mouse
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
power: 98mA chip-ID: 046d:c069 class-ID: 0301
Once we have that information, we can begin to suggest where to begin looking to resolve this issue.
Device-2: 1-8:37 info: Pixart Imaging Optical Mouse type: Mouse
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
power: 100mA chip-ID: 093a:2510 class-ID: 0301
Mine has same chipID as Cactus8284, working as expected. It came from WalMart with ONN branding.
# man inxi
ADMIN EXTRA DATA OPTIONS
These options are triggered with --admin or -a. Admin options
are advanced output options, and are more technical, and mostly
of interest to system administrators or other machine admins.
The --admin option sets -xxx, and only has to be used once. It
will trigger the following features:
...
<-a -J does not exist>
...
2: 07:00.1
class-ID: 0403
type: audio
# inxi --admin -xxx --usb
USB:
...
Device-1: 3-4:2 info: Pixart Imaging Optical Mouse type: Mouse
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
power: 100mA chip-ID: 093a:2510 class-ID: 0301
...
# inxi -a --usb
USB:
...
Device-1: 3-4:2 info: Pixart Imaging Optical Mouse type: Mouse
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
power: 100mA chip-ID: 093a:2510 class-ID: 0301
...
# inxi -Ja
USB:
...
Device-1: 3-4:2 info: Pixart Imaging Optical Mouse type: Mouse
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
power: 100mA chip-ID: 093a:2510 class-ID: 0301
...
#
IOW, either –admin or -a subsumes -xxx, and for some options, adds additional info, though not for -J aka –usb.
Then, it ain’t the hardware as such – the USB class-ID and kernel driver and USB speed is the same as for everyone else.
It could be, the USB connector – dirty contacts – use a Contact Spray (hardware components supplier) to clean both the contacts on the Mouse Cable connector and, those in the connector on the computer’s case.
Otherwise, something is interfering with the events being raised by your mouse:
> ls -l /dev/input/by-id/
total 0
drwxr-xr-x 2 root root 120 6. Mär 08:18 ./
drwxr-xr-x 4 root root 440 6. Mär 08:18 ../
lrwxrwxrwx 1 root root 9 6. Mär 08:18 usb-046a_0023-event-if01 -> ../event2
lrwxrwxrwx 1 root root 9 6. Mär 08:18 usb-046a_0023-event-kbd -> ../event1
lrwxrwxrwx 1 root root 9 6. Mär 08:18 usb-Logitech_USB_Laser_Mouse-event-mouse -> ../event0
lrwxrwxrwx 1 root root 9 6. Mär 08:18 usb-Logitech_USB_Laser_Mouse-mouse -> ../mouse0
>
The mouse on this system is using “event0”
> cat /proc/bus/input/devices | grep -A4 -B5 event0
I: Bus=0003 Vendor=046d Product=c069 Version=0110
N: Name="Logitech USB Laser Mouse"
P: Phys=usb-0000:01:00.0-10/input0
S: Sysfs=/devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb1/1-10/1-10:1.0/0003:046D:C069.0004/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: PROP=0
B: EV=17
B: KEY=ff0000 0 0 0 0
B: REL=1943
>
You can then use “evtest” (with the user “root”) to inspect the event stream being sent by your mouse – you’ll have to move the mouse:
# evtest --grab /dev/input/event0
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0xc069 version 0x110
Input device name: "Logitech USB Laser Mouse"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 272 (BTN_LEFT)
Event code 273 (BTN_RIGHT)
Event code 274 (BTN_MIDDLE)
Event code 275 (BTN_SIDE)
Event code 276 (BTN_EXTRA)
Event code 277 (BTN_FORWARD)
Event code 278 (BTN_BACK)
Event code 279 (BTN_TASK)
Event type 2 (EV_REL)
Event code 0 (REL_X)
Event code 1 (REL_Y)
Event code 6 (REL_HWHEEL)
Event code 8 (REL_WHEEL)
Event code 11 (REL_WHEEL_HI_RES)
Event code 12 (REL_HWHEEL_HI_RES)
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1678110072.987019, type 2 (EV_REL), code 0 (REL_X), value 1
Event: time 1678110072.987019, -------------- SYN_REPORT ------------
Event: time 1678110072.995014, type 2 (EV_REL), code 0 (REL_X), value 2
Event: time 1678110072.995014, type 2 (EV_REL), code 1 (REL_Y), value -1
Event: time 1678110072.995014, -------------- SYN_REPORT ------------
Event: time 1678110073.003014, type 2 (EV_REL), code 0 (REL_X), value 7
Event: time 1678110073.003014, type 2 (EV_REL), code 1 (REL_Y), value -2
Event: time 1678110073.003014, -------------- SYN_REPORT ------------
.
.
.
#
I just plugged my mouse into another USB port, now it works fine. As you said, maybe the problem was caused by dirty contacts in the old usb port. Thanks for your help.