You are not logged in.
When I start my computer the mouse works fine, as expected. After a day or 2 I start to notice the system does not register mouse clicks as reliably, maybe 5% are dropped. By a week or so of uptime it can get as bad as 50% of left mouse click are dropped.
Restarting always solves the problem.
Things that do not solve it:
* Switching from usb receiver to bluetooth
* Switching mice
* Switching usb ports (when using a corded or receiver mouse)
All firmware is up to date.
Problem started about 4 months ago, give or take a month. I have updated firmware and updated packages with pacman multiple times since then. I have even wiped the drive and re-installed arch to try to solve the problem.
The same mice have no problems on my other systems (though none of the others use arch, they have mint as they are systems I set up for my family to use)
Brand and model of mouse does not make a difference, nor does connection method.
Other linux (but not arch) laptops do not have the same problem with any of my mice.
Some system specs:
CPU: 16-core (6-mt/10-st) Intel Core Ultra 9 185H (-MST AMCP-)
speed/min/max: 400/400/4800:5100:3800:2500 MHz Kernel: 6.13.1-arch1-1 x86_64
Up: 7d 23h 3m Mem: 15.82/30.8 GiB (51.4%) Storage: 953.87 GiB (7.9% used)
Procs: 438 Shell: Zsh inxi: 3.3.37
0000:00:00.0 Host bridge: Intel Corporation Device 7d01 (rev 04)
0000:00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Arc Graphics] (rev 08)
0000:00:04.0 Signal processing controller: Intel Corporation Meteor Lake-P Dynamic Tuning Technology (rev 04)
0000:00:07.0 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 10)
0000:00:08.0 System peripheral: Intel Corporation Meteor Lake-P Gaussian & Neural-Network Accelerator (rev 20)
0000:00:0a.0 Signal processing controller: Intel Corporation Meteor Lake-P Platform Monitoring Technology (rev 01)
0000:00:0b.0 Processing accelerators: Intel Corporation Meteor Lake NPU (rev 04)
0000:00:0d.0 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 USB Controller (rev 10)
0000:00:0d.2 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0 (rev 10)
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
0000:00:12.0 Serial controller: Intel Corporation Meteor Lake-P Integrated Sensor Hub (rev 20)
0000:00:14.0 USB controller: Intel Corporation Meteor Lake-P USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
0000:00:14.2 RAM memory: Intel Corporation Device 7e7f (rev 20)
0000:00:14.3 Network controller: Intel Corporation Meteor Lake PCH CNVi WiFi (rev 20)
0000:00:15.0 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #0 (rev 20)
0000:00:15.2 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #2 (rev 20)
0000:00:15.3 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #3 (rev 20)
0000:00:16.0 Communication controller: Intel Corporation Meteor Lake-P CSME HECI #1 (rev 20)
0000:00:1f.0 ISA bridge: Intel Corporation Device 7e02 (rev 20)
0000:00:1f.3 Multimedia audio controller: Intel Corporation Meteor Lake-P HD Audio Controller (rev 20)
0000:00:1f.4 SMBus: Intel Corporation Meteor Lake-P SMBus Controller (rev 20)
0000:00:1f.5 Serial bus controller: Intel Corporation Meteor Lake-P SPI Controller (rev 20)
0000:01:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
0000:02:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
0000:02:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
0000:02:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
0000:02:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
0000:02:04.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03)
0000:04:00.0 PCI bridge: Intel Corporation JHL7440 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
0000:05:02.0 PCI bridge: Intel Corporation JHL7440 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
0000:06:00.0 USB controller: Intel Corporation JHL7440 Thunderbolt 3 USB Controller [Titan Ridge DD 2018] (rev 06)
0000:11:00.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01)
0000:12:01.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01)
0000:13:00.0 Ethernet controller: Aquantia Corp. AQtion AQC107S NBase-T/IEEE 802.3an Ethernet Controller [Atlantic 10G] (rev 02)
10000:e0:06.0 System peripheral: Intel Corporation RST VMD Managed Controller
10000:e0:06.2 PCI bridge: Intel Corporation Device 7ecb (rev 10)
10000:e1:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9C1a (DRAM-less)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 006: ID 8087:0b40 Intel Corp. USB3.0 Hub
Bus 002 Device 007: ID 0bda:0487 Realtek Semiconductor Corp. Dell dock
Bus 002 Device 008: ID 0bda:0413 Realtek Semiconductor Corp. Dell dock
Bus 002 Device 009: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 27c6:639c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 006: ID 0bda:5583 Realtek Semiconductor Corp. Integrated_Webcam_FHD
Bus 003 Device 008: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
Bus 003 Device 011: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 003 Device 016: ID 1d5c:5801 Fresco Logic USB2.0 Hub
Bus 003 Device 017: ID 0bda:5487 Realtek Semiconductor Corp. Dell dock
Bus 003 Device 018: ID 0bda:5413 Realtek Semiconductor Corp. Dell dock
Bus 003 Device 019: ID 413c:b06e Dell Computer Corp. Dell dock
Bus 003 Device 020: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 003 Device 021: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 022: ID 413c:b06f Dell Computer Corp. Dell dock
Bus 003 Device 023: ID 1050:0010 Yubico.com Yubikey (v1 or v2)
Bus 003 Device 024: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A)
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0b00:5483 INGENICO 4-Port USB 2.0 Hub
Bus 005 Device 003: ID 0bda:5483 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 005 Device 004: ID 0bda:1100 Realtek Semiconductor Corp. USB2.0 HID
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 0b00:0483 INGENICO 4-Port USB 3.0 Hub
Bus 006 Device 003: ID 0bda:0483 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 006 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Offline
After a day or 2 I start to notice the system does not register mouse clicks as reliably, maybe 5% are dropped. By a week or so of uptime it can get as bad as 50% of left mouse click are dropped.
First I'd check whether clicks are dropped before or after UI. Run
xev -event mouse -1 | grep ButtonClick on the window and check whether click events are dropped. If they are, check input subsystem then. Find which /dev/input/event* corresponds to your mouse:
sudo libinput list-devicesThen run
sudo libinput debug-events /dev/input/eventX | grep POINTER_BUTTONwhere eventX is your mouse event node.
Offline
Based on what I am seeing with those commands it looks like what is happening is that press and/or release events occasionally are delayed by half a second or so. But I only see this with xev, not with libinput. When it does happen, the release is the one that is usually delayed, but much more rarely the initial press is delayed.
This also explains something I noticed earlier today, sometimes when my click is delayed text gets highlighted in the direction I moved the mouse, very briefly, as though I was selecting test with a pressed button, even though I let it go immediately.
This helps hone in on the issue, but still not sure how to fix it.
Offline
I just installed aur/xf86-input-libinput-git to se eif that helps, now I have to let the computer sit turned on for a couple days to see if the issue resurfaces...
Offline
Nope, the different driver did not fix it.
Offline