Description of problem: It started crashing after updating my system and rebooting. Notable packages in the list were Qt (6.10.1) and linux-firmware (2025-11-11). I searched online and found a bug report for Arch Linux with the same issue. Version-Release number of selected component: plasma-workspace-6.5.3-1.fc43 Additional info: reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGSEGV journald_cursor: s=269491f157a34f36b39d73a7db64915d;i=97e8d;b=89a12f03843f4145b303fc4521905dd0;m=3509acf;t=6443f67df5035;x=b542e4e67dda1e8f executable: /usr/bin/plasmashell cmdline: /usr/bin/plasmashell --no-respawn rootdir: / uid: 1000 kernel: 6.17.8-300.fc43.x86_64 package: plasma-workspace-6.5.3-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler comment: It started crashing after updating my system and rebooting. Notable packages in the list were Qt (6.10.1) and linux-firmware (2025-11-11). I searched online and found a bug report for Arch Linux with the same issue. Truncated backtrace: Thread no. 0 (1 frames) #3 KCrash::defaultCrashHandler at /usr/src/debug/kf6-kcrash-6.20.0-1.fc43.x86_64/src/kcrash.cpp:605 Potential duplicate: bug 2263057
Created attachment 2115837 [details] File: proc_pid_status
Created attachment 2115838 [details] File: maps
Created attachment 2115839 [details] File: limits
Created attachment 2115840 [details] File: cgroup
Created attachment 2115841 [details] File: environ
Created attachment 2115842 [details] File: open_fds
Created attachment 2115843 [details] File: mountinfo
Created attachment 2115844 [details] File: os_info
Created attachment 2115845 [details] File: cpuinfo
Created attachment 2115846 [details] File: core_backtrace
Created attachment 2115847 [details] File: dso_list
Created attachment 2115848 [details] File: var_log_messages
Created attachment 2115849 [details] File: backtrace
It happened after the latest Fedora 43 updates on 23 NOV. However, I think it's related to the settings I had for the "Digital Clock" plasmoid. I was able to recover from the crashes by removing the plasmashellrc and plasma-org.kde.plasma.desktop-appletsrc. On reconfiguring I was able to reproduce a crash by turning on either the "Astronomical Events" or "Holidays" calendar. reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGSEGV journald_cursor: s=2d837d3aeebd4f54ace032d4568f22a9;i=4c5d88;b=a8d52196b3ff424cb8ba5c7cbd1316c0;m=56f746af;t=644467bb908e4;x=16defbcbc9a13849 executable: /usr/bin/plasmashell cmdline: /usr/bin/plasmashell cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-\x2fusr\x2fbin\x2fplasmashell rootdir: / uid: 1000 kernel: 6.17.8-300.fc43.x86_64 package: plasma-workspace-6.5.3-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler comment: It happened after the latest Fedora 43 updates on 23 NOV. However, I think it's related to the settings I had for the "Digital Clock" plasmoid. I was able to recover from the crashes by removing the plasmashellrc and plasma-org.kde.plasma.desktop-appletsrc. On reconfiguring I was able to reproduce a crash by turning on either the "Astronomical Events" or "Holidays" calendar.
Created attachment 2115926 [details] plasma-org.kde.plasma.desktop-appletsrc Configuration that can cause the crash
As at https://bugs.kde.org/show_bug.cgi?id=512532#c0: > After invoking `sudo dnf5 upgrade --refresh --offline && sudo dnf5 offline > reboot`, `plasmashell` repeatedly crashed. reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGSEGV journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=42fcef;b=1485f1d0f2ca4c14b3346a33f44d96e0;m=e58c26c4;t=64449b14b6714;x=f7645bf1052451b6 executable: /usr/bin/plasmashell cmdline: /usr/bin/plasmashell --no-respawn cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-plasmashell.service rootdir: / uid: 1000 kernel: 6.17.8-300.fc43.x86_64 package: plasma-workspace-6.5.3-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler
*** This bug has been marked as a duplicate of bug 2416624 ***
(In reply to Andreas Schneider from comment #17) > > *** This bug has been marked as a duplicate of bug 2416624 *** Sorry to be nitpicking, but shouldn't it be the other way around? I believe I filed the report earlier.
That's not the sole determiner – the now-authoritative bug contains an explanation, has the upstream ticket linked, and provides a debugged trace in its #c1. Based upon its comments, it's also where the work is being tracked.
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #19) > That's not the sole determiner – the now-authoritative bug contains an > explanation, has the upstream ticket linked, and provides a debugged trace > in its #c1. Based upon its comments, it's also where the work is being > tracked. Oh, okay. Thanks for clarifying. I am pretty new to this.
No worries. I'd still have said the same if it had been my bug. 😁