Windows sticking to cursor, mouse buttons sticking in game

Hello Garuda fam,

First i want to thank you all for the help you've given me with latte. I'm diving a lot deeper into everything.

I have unfortunately no clear timeline in which this started happening (i know that is key). However, I'm experiencing windows "sticking" to my mouse cursor as though I'd never let go of my left mouse button. Brave is a particular offender (EDIT: when I drag a tab off a window to open a new one), but it happens with terminal and dolphin too.

I also notice occasionally that in final fantasy xiv, both of my mouse buttons get "software stuck" down giving an auto-run that is difficult to break in the middle of combat. I've walked off the edge of a platform in raids as tank a few times and that has caused much frustration in my group of friends. "There she goes jumping off a cliff again..."

Are there any known offenders that do this I could look into?

System:
Kernel: 5.16.4-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f6cccf9c-8580-435e-8f33-927e3e31bb2d rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=2e9cba84-8fd3-4884-995e-6ac1c54716ad loglevel=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF
serial: <superuser required>
Mobo: Gigabyte model: X570 AORUS ELITE v: x.x
serial: <superuser required> UEFI: American Megatrends LLC. v: F34
date: 06/10/2021
Battery:
ID-1: hidpp_battery_1 charge: 33% condition: N/A volts: 3.8 min: N/A
model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
serial: <filter> status: Discharging
CPU:
Info: model: AMD Ryzen 9 3950X bits: 64 type: MT MCP arch: Zen 2
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB
L3: 64 MiB desc: 4x16 MiB
Speed (MHz): avg: 3674 high: 4301 min/max: 2200/4761 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3492 2: 3965
3: 4103 4: 4301 5: 3596 6: 3688 7: 3746 8: 3566 9: 3596 10: 3591 11: 3588
12: 3588 13: 3596 14: 3591 15: 3594 16: 3583 17: 3564 18: 4160 19: 3593
20: 3592 21: 3563 22: 3592 23: 3587 24: 3548 25: 3590 26: 3590 27: 3585
28: 4075 29: 3520 30: 3699 31: 3543 32: 3597 bogomips: 223568
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Micro-Star MSI
driver: nvidia v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 0a:00.0
chip-ID: 10de:1e84 class-ID: 0300
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 5120x1440 s-dpi: 107 s-size: 1216x342mm (47.9x13.5")
s-diag: 1263mm (49.7")
Monitor-1: DP-2 res: 2560x1440 dpi: 109 size: 598x336mm (23.5x13.2")
diag: 686mm (27")
Monitor-2: DP-4 res: 2560x1440 dpi: 109 size: 597x336mm (23.5x13.2")
diag: 685mm (27")
OpenGL: renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
v: 4.6.0 NVIDIA 495.46 direct render: Yes
Audio:
Device-1: YUAN High-Tech Development vendor: Corsair Memory driver: N/A
bus-ID: 06:00.0 chip-ID: 12ab:0380 class-ID: 0480
Device-2: NVIDIA TU104 HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 0a:00.1 chip-ID: 10de:10f8
class-ID: 0403
Device-3: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus-ID: 0c:00.4 chip-ID: 1022:1487
class-ID: 0403
Device-4: Texas Instruments ATH-G1WL type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-3.1.4:13
chip-ID: 0451:16ba class-ID: 0300 serial: <filter>
Sound Server-1: ALSA v: k5.16.4-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.44 running: yes
Network:
Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
port: f000 bus-ID: 05:00.0 chip-ID: 8086:1539 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 4.57 TiB used: 493.31 GiB (10.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: A-Data model: SX6000PNP
size: 953.87 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: V9002s85
temp: 42.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T1XHE-00AFY0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 614600WD temp: 58.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 4B6Q scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD20EARX-00ZUDB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 0A80 scheme: GPT
Partition:
ID-1: / raw-size: 896.73 GiB size: 896.73 GiB (100.00%) used: 47 GiB (5.2%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 896.73 GiB size: 896.73 GiB (100.00%)
used: 47 GiB (5.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 896.73 GiB size: 896.73 GiB (100.00%)
used: 47 GiB (5.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 896.73 GiB size: 896.73 GiB (100.00%)
used: 47 GiB (5.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.35 GiB used: 52 MiB (0.2%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.49 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 42.0 C mobo: 41.0 C gpu: nvidia temp: 75 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 69%
Info:
Processes: 542 Uptime: 1d 2h 57m wakeups: 40 Memory: 31.35 GiB
used: 9.38 GiB (29.9%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1920 lib: 529 Shell: fish
v: 3.3.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.12
Garuda (2.5.3-1):
System install date:     2022-01-22
Last full system update: 2022-02-01
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:            bluetooth-autoconnect.service

:laughing:

Have you been using that mouse for a while? It sounds like it might need a fresh battery.

1 Like

Would 25-35% really do it? Seems like it happens even when fully charged.

Hmm, no then I would say that was just a bad guess on my part. I did not realize the mouse is rechargeable.

Does the mouse have a USB dongle thingie, or is it bluetooth?

It's got a tiny USB dongle.

Fancy:

LIGHTSPEED Wireless

image

Just as a troubleshooting question: if you use the mouse in wired mode, can you reproduce the issue?

You might not want to hear this, but this article suggests that Logitec has kind of an ongoing problem with sometimes using a specific crappy switch that can produce functionality issues like you describe. It sounds like it tends to get worse over time as the switch continues to be used.

The article lays out a fix, but it involves replacing the switches and does not look like a simple job (soldering iron required for certain models, for example).

1 Like

I'll have to try. Since it's intermittent it may indeed have a cause like a degrading switch...

It does come with graphical delays and stutters when it happens in KDE with Brave, so I was thinking it was more of a software issue, maybe x11. I'll keep trying to reproduce in various ways i guess!

I used to help friends solder badges for CypherCon, so I hope it's something easy like that...

1 Like

Why don't you swap in an alternate mouse for troubleshooting purposes. A USB mouse would be preferable as that will remove the wireless component from the equation. If an alternate mouse works correctly that increases the odds substantially that your mouses hardware is failing.

There is also software in the AUR that supports many Logitech devices, have you checked on if your device is supported?

3 Likes

I haven't checked to see if my device is supported, i will do this! Thank you! I have limited access to other replacements to try, i'll see if i can bring one home from work.

It's intermittent still, so I'm thinking this is going to be a very hard issue to troubleshoot. :frowning:

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.