Bug 514129

Summary: KDE-Plasma will lock up and fail to start on Intel Battlemage dGPU (B580) on kernel 6.18+
Product: [Plasma] plasmashell Reporter: set2minecraft
Component: Startup processAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: grave CC: kde, nate
Priority: NOR    
Version First Reported In: 6.5.4   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: gdb log session when I attempted to debug

Description set2minecraft 2026-01-03 22:49:08 UTC
Created attachment 188200 [details]
gdb log session when I attempted to debug

SUMMARY
Kde plasma (wayland only tested) will not start with linux kernel 6.18 or above. it will start and run fine with 6.17 or earlier. This only happens with my intel B580 Graphics Card. This does not happen with integrated Ryzen 9000 or iris graphics 80EU. This only affects KDE (sway, xfce, niri, hyprland work without issue). Down grading Kernel to 6.17.9.arch1-1 will fix this (not much of a fix). Versions 6.18.2.arch2-1 and 6.18.3.arch1-1 cause this. I do not have older kernel versions currently to test with

STEPS TO REPRODUCE
1. upgrade kernel to 6.18 (or higher)
2. attempt to start kde plasma (weather from sddm or tty[startplasma-wayland])
3. nothing happens after successful login, tty session freezes

OBSERVED RESULT
System locks up, this includes switching to a seperate tty on the same screen. HOWEVER, ssh works in this state so the system can be observed and recovered. restarting sddm will unfreeze the system if plasma was started from sddm


EXPECTED RESULT
KDE plasma to load normally


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
running startplasma-wayland with gdb showed my nothing
Comment 1 Nate Graham 2026-01-06 18:04:19 UTC
This seems like a problem beneath us in the stack, and having to do with buggy graphics drivers.

Can you please report this to the Mesa developers? See https://docs.mesa3d.org/bugs.html