Bug 479913

Summary:	Entire system froze and stopped responding, not even Ctrl+Alt+F<N> worked
Product:	[Plasma] plasmashell	Reporter:	php4fan
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	kde, nate, nicolas.fella
Priority:	NOR
Version First Reported In:	5.27.9
Target Milestone:	1.0
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description php4fan 2024-01-16 19:36:26 UTC

SUMMARY

I had several applications running.
Chrome started behave strangely, and then the entire system froze stopped responding to keyboard and mouse.

The mouse cursor wouldn't move. No key or combination of keys would do anything.

Not even Ctrl+Alt+F1/2/3/4 worked, so I couldn't even open a virtual console and see if some process was consuming CPU or whatever.

The only thing I managed to do was a REISUB.

Obviously this caused me to lose a huge amount of unsaved work.

Please tell me what logs I can fetch that may help you investigate the issue.
Of course I cannot tell for sure the issue is in KDE, but I feel like that's where I'd start looking.

STEPS TO REPRODUCE

no idea.


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
Kernel Version: 6.1.68-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 7.3 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: LENOVO
Product Name: 81WE
System Version: IdeaPad 3 15IIL05

Comment 1 php4fan 2024-01-16 20:10:30 UTC

How is the entire system completely freezing anything less that critical??

Comment 2 Nate Graham 2024-01-16 20:17:17 UTC

That sounds like it sucks.

However since you're using X11, we can rule out KDE code, since on X11, only the X server has the power to freeze the system as completely as you've described.

Unfortunately the X server is essentially unmaintained so I doubt anyone over there who you could report the bug to would be able to troubleshoot it, let alone fix it. In the future I'd recommend using Wayland since it's much more debuggable from a KDE perspective, and you're much more likely to end up with the issue being investigated an fixed.