Bug 509453 - Plasmashell keeps crashing, on startup, or on click onto the panel [BACKTRACE]
Summary: Plasmashell keeps crashing, on startup, or on click onto the panel [BACKTRACE]
Status: RESOLVED DUPLICATE of bug 509192
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.4.4
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-13 09:17 UTC by Jens
Modified: 2025-10-06 20:25 UTC (History)
3 users (show)

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


Attachments
Backtrace: coredumpctl debug plasmashell -A "-ex bt -ex quit" (51.89 KB, text/plain)
2025-09-13 09:17 UTC, Jens
Details
new backtrace using coredumpctl (81.45 KB, text/plain)
2025-09-14 15:17 UTC, Jens
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jens 2025-09-13 09:17:02 UTC
Created attachment 184931 [details]
Backtrace: coredumpctl debug plasmashell -A "-ex bt -ex quit"

SUMMARY: see $SUBJECT
100% repeatable, happens daily since about a week ago. Computer hardly usable.

STEPS TO REPRODUCE
1. Start computer with KDE and autologin
2. Watch panel appear & disappear a few times with "drkonqi" windows appearing
3. Then, only a mouse cursor on a black screen remains. I can log out (power button) and restart, but nothing else.
4. With some luck, on the second login attempt it doesn't crash. (like now as I'm typing this)

OBSERVED RESULT
See above

EXPECTED RESULT
KDE should start up normally.
If there is some configuration corruption or leftover temp files or something, Plasmashell should be robust enough to deal with this cleanly.

Last line of attached backtrace:
#44 0x00005f2cf4c89638 in main (argc=<optimized out>, argv=<optimized out>)
    at /usr/src/plasma-workspace-4:6.4.4-0zneon+24.04+noble+release+build48/shell/main.cpp:188

SOFTWARE/OS VERSIONS: (from Info center)
KDE Neon 6.3 with KDE Plasma 6.4.4 and all current updates installed.
Operating System: KDE neon User Edition
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.14.0-29-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-1370P
Memory: 32 GiB of RAM (31.0 GiB usable)
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: LENOVO
Product Name: 21HJS06H00
System Version: ThinkPad T16 Gen 2

ADDITIONAL INFORMATION
In case this is relevant - my bottom task panel contains (L->R) the following widgets:
virtual desktops, CPU, RAM & Temperature load, app starter, icon only taskbar, notification area, clock, "show desktop" icon.
This has been going on for some time, at least since 6.4.3.
Comment 1 Jens 2025-09-13 09:47:58 UTC
Update: the series of endless crashes also happens after a resume from standby.
The crash series stopped after I removed the system monitor widgets from my taskbar.
Something in there was majorly broken, it seems.
Using the supplied backtrace, is this tracable to the system monitor widget?
Comment 2 Jens 2025-09-14 15:17:36 UTC
Created attachment 184953 [details]
new backtrace using coredumpctl

Update: Upgrading to Plasma 6.4.5 does not fix this problem, nor does removing and reconfiguring the system load widget on the taskbar (which I had suspected).
Crashes keep happening until I have >20 drkonqi processes trying to generate backtraces in parallel and /tmp is full (1.5GB) which basically grinds the system to a complete halt. There should be a maximum number of parallel drkonqi processes allowed to run.
New backtrace attached.
Comment 3 Jens 2025-09-14 17:08:33 UTC
Update: This happens also on an X11 session, so it does not seem to be Wayland related.
Comment 4 Jens 2025-09-16 17:23:25 UTC
Removing plasmashellrc plasma-org.kde.plasma.desktop-appletsrc  in ~/.config - and reconfiguring the panel with my favorite settings, but without any extra applets - seems to fix the issue until the next restart, but then the crashes happen again.

I am now keeping the configuration default as is after removing the above two files, no additional applets, and will report back when/if it crashes again.
Comment 5 TraceyC 2025-09-16 21:23:23 UTC
Thank you for the bug report. 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:

#14 0x000077b0fa546e39 n/a (libQt6Core.so.6 + 0x346e39)
#10 0x000077b0fb8e1225 n/a (libQt6Qml.so.6 + 0x4e1225)
#20 0x000077b0fbebdf5b n/a (libQt6Quick.so.6 + 0x4bdf5b)
#4  0x000077b0f2fe10da n/a (libQt6QuickTemplates2.so.6 + 0x1e10da)
#31 0x0000604af1e47638 n/a (plasmashell + 0x3d638)

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!
Comment 6 Bug Janitor Service 2025-10-01 03:46:36 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Jens 2025-10-06 20:23:11 UTC
I'd love to install the debug symbols. Please tell me how specifically to do this for KDE Neon. The website lists a debug server which doesn't (seem to) provide the correct info, drkonqi tries to download "additional information" (debug symbols) but never finishes, and the Ubuntu dbgsym server provides libqt6 6.4, while Neon uses v6.9.

Please tell me how specifically to do this for KDE Neon for the qt6 packages which require it.
Thank you!
Comment 8 Antonio Rojas 2025-10-06 20:25:51 UTC

*** This bug has been marked as a duplicate of bug 509192 ***