Bug 509578

Summary: Plasma shell crash, from bluetooth tray icon.
Product: [Plasma] plasmashell Reporter: fbm224
Component: Bluetooth widgetAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: fbm224, nate
Priority: NOR    
Version First Reported In: 6.4.5   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Dr. Konqi detailed report.
coredumpctl gdb plasmashell process.

Description fbm224 2025-09-17 01:44:02 UTC
Created attachment 184993 [details]
Dr. Konqi detailed report.

SUMMARY
I get a plasma shell error report by dr konqi  after trying to open the Bluetooth from the task bar to connect to a device (speakers). 

STEPS TO REPRODUCE
1. After login, click on Bluetooth icon on sys tray. (annoyingly it does not always happen).
 
OBSERVED RESULT
Dr. Konqi reports a plasmashell crash.  Attached detailed report. 
Some times it repeats, and fails to re open plasma shell, which leaves no desktop background, and no panels.  I reboot from the terminal . 

EXPECTED RESULT
Bluetooth devices list opens from the tray, 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSuse Tumbleweed
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
Comment 1 fbm224 2025-09-17 01:47:27 UTC
It began after updating to the 20250817 snapshot from 20250808. I've since updated to 20250910 with same results.
Comment 2 Nate Graham 2025-09-17 15:03:08 UTC
Sorry this happened. Unfortunately it looks like the backtrace is mangled and unusable. Can you try to get one manually? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 3 fbm224 2025-09-17 19:03:20 UTC
Created attachment 185021 [details]
coredumpctl gdb plasmashell process.
Comment 4 Nate Graham 2025-09-18 19:27:03 UTC
Thanks! This is Bug 509192, which is being actively investigated and fixed today.

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