Bug 504593

Summary:	KWin Wayland DRM - Thread hangs when middle mouse button (scroll wheel) pressed.
Product:	[Plasma] kwin	Reporter:	isaac17percy <isaac17percy>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kdedev
Priority:	NOR
Version First Reported In:	6.3.5
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Compressed strace of kwin log journalctf of crash

Description isaac17percy@gmail.com 2025-05-21 03:33:22 UTC

SUMMARY


STEPS TO REPRODUCE
1. Open a window
2. Press middle click on mouse
3. Move mouse up/down

OBSERVED RESULT
Entire OS hangs. I've found turning one monitor off and on again seems to somewhat resolve it, or it may just be a time thing.  

EXPECTED RESULT
Should scroll the window, not hang the whole system. 

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070


ADDITIONAL INFORMATION

I have a wireless Zowie Ec-1 mouse. It has worked fine before, but now the middle click causes a crash. I'm not sure why, but it's reproducible 9/10 times on my system. 

Also, my journalctf log reports: 
May 20 21:12:42 IsaacsArchPC kwin_wayland[845]: kwin_wayland_drm: The main thread was hanging temporarily!

Whenever the hang occurs. See the attached file for the strace of the kwin process.

Comment 1 isaac17percy@gmail.com 2025-05-21 03:36:08 UTC

Created attachment 181591 [details]
Compressed strace of kwin log

Comment 2 isaac17percy@gmail.com 2025-05-21 03:36:36 UTC

Created attachment 181592 [details]
journalctf of crash

Comment 3 Vlad Zahorodnii 2025-05-21 07:33:16 UTC

Anything in dmesg logs? It seems like a kernel or a libinput issue.

Comment 4 isaac17percy@gmail.com 2025-05-22 20:56:49 UTC

(In reply to Vlad Zahorodnii from comment #3)
> Anything in dmesg logs? It seems like a kernel or a libinput issue.

I believe you are correct that it is likely a kernel or libinput issue, as after turning it on and off the issue was gone. Next time it shows up I will report it to the correct area. 

Thanks!!