Mouse does double clicks

Ask Fedora
, , ,
1

I’m Fedora 42 KDE desktop on ASUS Strix X570-E motherboard with Nvidia graphics on 6.18.7-100.fc42.x86_64. And in the last few releases (not sure which one it started on) I’m getting double or multiple clicks from my wireless mouse. The mouse is one I’ve had for several years and used on several Fedora releases, it is a logitech M310. It is really annoying.

How to I determine where this problem is coming from? I’ve looked through the KDE settings but can’t find anything that I think is related.

Anyone else seen this type issue and how did you fix.

Thanks in advance for any help.

2

For me it was a warn out mouse and getting a new mouse fixed the problem.

3

this is the first wireless mouse that I’ve had and wasn’t sure how they behave. I’ve used corded mice for years and never worn out one. Just had to clean the ball a few times.

4

I assume that mouse uses the logitek unified receiver as I do. It is possible that the firmware in the receiver needs updated.

It is also possible that the mouse needs new batteries. When the power gets low in the mouse the connection to the receiver becomes erratic and can do unexpected things.

5

The battery show 55% on KDE Power and Battery app. I don’t know about the logitek unified receiver. How do I check if that’s what I have and the firmware I’m using. Also how would I get updated firmware. The motherboard is running the latest non beta firmware.

6

I’d try the mouse on a different computer (if it happens there it’s probably the mouse)

Some mice have a debounce option (firmware updates might change it, or it might unexpectedly change based on a profile on how it’s connected to a computer); increasing it could help (my mouse defaults 3ms and maxes 10 or 15ms).

I’d sooner suspect the mouse, but any USB stack changes might do something like consolidate/delay USB packets (AMD/chipset/mobo-side, OS USB driver), or might do odd things depending on where the USB port is connected (Ryzen has something like CPU-side and chipset-side; chipset’s slower), and might get more fun if IOMMU is involved or bad OC or RAM settings (I’ve seen it all X470 :stuck_out_tongue:)

1 Like
7

Use the sudo fwupdmgr update command.

$ sudo fwupdmgr update
Devices with the latest available firmware version:
 • UEFI CA
 • UEFI dbx
 • Unifying Receiver
Devices with no available firmware updates:
 • CT2000P5PSSD8
 • KEK CA
 • Option ROM UEFI CA
 • SBAT
 • ST4000VN008-2DR166
 • ST4000VN008-2DR166
 • ST4000VN008-2DR166
 • ST8000VN004-2M2101
 • Windows Production PCA

Your mouse is shown here and the box content should have been this

image
image240×203 3.13 KB

If you have never replaced the battery or it has been some time since the battery was replaced that should be your first step.

8

Yes I’ve replaced the battery a couple of times over the years. I purchased a new logitech M310 mouse and it doesn’t work at all. However I switched back to the original mouse and ran the “fwupdmgr update” command and it seems to have made a difference. I need to wait a couple of days and see if I continue to see problems.. I have never ran that command and didn’t know about it. I think it updated some things and then rebooted. Is something I should be running periodically?