Bug 501559

Summary:	Crash With The Plasmashell.
Product:	[Plasma] plasmashell	Reporter:	Rashaud <rashaudwhittle>
Component:	"Manage Desktop and Panels" window	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	cwo.kde
Priority:	NOR
Version First Reported In:	6.3.2
Target Milestone:	1.0
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rashaud 2025-03-16 02:20:19 UTC

System Information:
- OS: Debian Trixie
- Kernel: 6.12.17-amd64
- Architecture: x86_64
- KDE Plasma Version: 6.3.2
- Memory: 15GB RAM (4.2GB used, 11GB available)
- Swap: 12GB (barely used)

Crash Pattern:
Multiple crashes observed with the following pattern:
- 2025-03-15 20:06:50 EDT - SIGSEGV (2.5M)
- 2025-03-15 20:07:07 EDT - SIGSEGV (2.6M)
- 2025-03-15 21:51:25 EDT - SIGSEGV (2.5M)
- 2025-03-15 21:54:11 EDT - SIGSEGV (2.5M)
- 2025-03-15 22:02:23 EDT - SIGSEGV (2.5M)

Steps to Reproduce:
1. Normal desktop usage leads to random crashes
2. Plasmashell restarts automatically but continues to crash
3. Even checking version (plasmashell --version) triggers segfault

Temporary Workaround:
- Resetting plasma configuration files temporarily resolves the issue
- But crashes eventually return

Relevant Package Versions:
- kde-cli-tools: 4:6.3.2-1+b1
- kde-cli-tools-data: 4:6.3.2-1
- kde-config-gtk-style: 4:6.3.2-1+b2
- kde-config-screenlocker: 6.3.2-1+b1
- kde-config-updates: 6.3.2-1

Comment 1 cwo 2025-03-16 11:03:39 UTC


If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!

Then mark it as NEEDSINFO BACKTRACE

Comment 2 Bug Janitor Service 2025-03-31 03:46:53 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 3 Bug Janitor Service 2025-04-15 03:46:55 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.