Bug 514264 - KWin Wayland freezes requiring reboot on KDE Neon/Ubuntu, with plasmashell SEGV
Summary: KWin Wayland freezes requiring reboot on KDE Neon/Ubuntu, with plasmashell SEGV
Status: NEEDSINFO BACKTRACE
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.5.4
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-07 09:45 UTC by mahdsip
Modified: 2026-01-07 17:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
trace (52.41 KB, text/plain)
2026-01-07 09:45 UTC, mahdsip
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mahdsip 2026-01-07 09:45:02 UTC
Created attachment 188286 [details]
trace

## Summary
Plasmashell crashes continuously (every 2-3 seconds) due to Qt6WebEngineCore segmentation fault. The crash loop generates 112,678+ QThreadStorage cleanup errors over 31 hours. After prolonged instability, this triggers KWin Wayland DPMS failures with "Atomic modeset test failed!" errors, causing complete system freeze requiring hard reboot.

## Steps to Reproduce
1. System running normally on KDE Plasma Wayland session
2. Plasmashell begins crashing repeatedly (every 2-3 seconds)
3. After extended crash loop (multiple hours), KWin starts failing atomic modeset operations
4. System becomes completely unresponsive
5. Only hard reboot recovers the system

## Expected Behavior
1. Plasmashell should run stably without crashing
2. If plasmashell crashes, it should either recover cleanly or stop attempting to restart
3. KWin should handle display power management (DPMS) operations gracefully even if plasmashell is unstable

## Actual Behavior
1. Plasmashell enters a crash loop, restarting every 2-3 seconds
2. Each crash generates QThreadStorage cleanup warnings (entries 1, 2, and 7)
3. Over 112,678 crash cycles occur during a 31-hour session
4. Eventually, KWin enters an infinite loop of failed atomic modeset attempts
5. System freezes completely

## System Information
- **Operating System**: KDE neon User Edition
- **KDE Plasma Version**: 6.5.4
- **KWin Version**: 6.5.4
- **Qt Version**: 6.10.1
- **Qt WebEngine Version**: 6.10.1-0zneon+24.04+noble+release+build41
- **Kernel Version**: 6.14.0-37-generic
- **Graphics Platform**: Wayland
- **GPU**: Intel Alder Lake-P GT2 [Iris Xe Graphics] (rev 0c)
- **GPU Driver**: i915 (kernel module)
- **Display**: DP-1 connected, 1920x1080

## Relevant Log Excerpts

### Plasmashell crash loop (throughout entire session):
```
Jan 05 07:44:21 bmaxB9 plasmashell[2949]: QThreadStorage: entry 7 destroyed before end of thread
Jan 05 07:44:21 bmaxB9 plasmashell[2949]: QThreadStorage: entry 2 destroyed before end of thread
Jan 05 07:44:21 bmaxB9 plasmashell[2949]: QThreadStorage: entry 1 destroyed before end of thread
Jan 05 07:44:22 bmaxB9 plasmashell[3174]: QThreadStorage: entry 7 destroyed before end of thread
[... repeated 112,678+ times over 31 hours ...]
```

### KWin failures (final stage before freeze, Jan 6 15:02:07-15:02:10):
```
Jan 06 15:02:07 bmaxB9 kwin_wayland[1417]: Atomic modeset test failed! Invalid argument
Jan 06 15:02:07 bmaxB9 kwin_wayland[1417]: Setting dpms mode failed!
[... repeated hundreds of times ...]
```

### Pattern observed:
- Plasmashell crashes and restarts every 2-3 seconds (note changing PIDs: 2949→3174→3224→3262...)
- Each crash generates 3 QThreadStorage cleanup warnings
- "There are no outputs - creating placeholder screen" messages appear during crashes
- After ~31 hours of crash loop, KWin DPMS operations begin failing
- System becomes unresponsive shortly after KWin error flood begins
Comment 1 TraceyC 2026-01-07 17:45:33 UTC
Thank you for the bug report and the backtrace. I'm not able to reproduce this on git-master. Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

                #24 0x000079c7ed549d72 n/a (libQt6WebEngineCore.so.6 + 0x1b49d72)
                #29 0x000079c89fc8852f n/a (libQt6Core.so.6 + 0x28852f)

Could you please install debug packages and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!