Bug 2411800

Summary: [abrt] plasma-workspace: KCrash::defaultCrashHandler(): plasmashell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: cherkaba
Component: plasma-workspaceAssignee: KDE SIG <kde-sig>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 43CC: 8ru2u4gz, cherkaba, jgrulich, kde-sig, marcdeop, stealthcipher, than, viniciush.dev
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/dcd37fa3dd881ade89bd5d0951db9c7766595c7
Whiteboard: abrt_hash:5ad41f2383dd4c180a52c795cca0a81d0f012026;VARIANT_ID=kde;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: var_log_messages
none
File: backtrace
none
File: environ none

Description cherkaba 2025-11-01 20:40:29 UTC 
Version-Release number of selected component:
plasma-workspace-6.5.1-1.fc43

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGSEGV
journald_cursor: s=8297339ffd124c1aa801d094d4bbd5f0;i=f2e11e3;b=d236a99f660e4b06b70a9c19f4b78fb4;m=1a4f58348;t=6428d83cabd01;x=a71b8f0587843149
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.5-300.fc43.x86_64
package:        plasma-workspace-6.5.1-1.fc43
runlevel:       /bin/sh: ligne 1: runlevel: commande introuvable
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler

Truncated backtrace:
Thread no. 1 (1 frames)
 #3 KCrash::defaultCrashHandler at /usr/src/debug/kf6-kcrash-6.19.0-1.fc43.x86_64/src/kcrash.cpp:605


Potential duplicate: bug 2269942
Comment 1 cherkaba 2025-11-01 20:40:33 UTC 
Created attachment 2111872 [details]
File: proc_pid_status
Comment 2 cherkaba 2025-11-01 20:40:35 UTC 
Created attachment 2111873 [details]
File: maps
Comment 3 cherkaba 2025-11-01 20:40:36 UTC 
Created attachment 2111874 [details]
File: limits
Comment 4 cherkaba 2025-11-01 20:40:38 UTC 
Created attachment 2111875 [details]
File: open_fds
Comment 5 cherkaba 2025-11-01 20:40:39 UTC 
Created attachment 2111876 [details]
File: mountinfo
Comment 6 cherkaba 2025-11-01 20:40:40 UTC 
Created attachment 2111877 [details]
File: os_info
Comment 7 cherkaba 2025-11-01 20:40:41 UTC 
Created attachment 2111878 [details]
File: cpuinfo
Comment 8 cherkaba 2025-11-01 20:40:44 UTC 
Created attachment 2111879 [details]
File: core_backtrace
Comment 9 cherkaba 2025-11-01 20:40:46 UTC 
Created attachment 2111880 [details]
File: dso_list
Comment 10 cherkaba 2025-11-01 20:40:47 UTC 
Created attachment 2111881 [details]
File: var_log_messages
Comment 11 cherkaba 2025-11-01 20:40:48 UTC 
Created attachment 2111882 [details]
File: backtrace
Comment 12 cherkaba 2025-11-01 20:40:50 UTC 
Created attachment 2111883 [details]
File: environ
Comment 13 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-11-09 17:51:32 UTC 
As https://bugs.kde.org/show_bug.cgi?id=511874#c0 explains, "Without any noticeable interaction from me, the sole visible panel hung. (I neglected to confirm whether the desktop was impacted, but I presume so.) To remediate this, I issued the "Log out" command via KRunner. This appeared to do nothing, so I repeated it. The sound for the first invocation played 15 s late, but I solely heard it once. 3 s after that, I invoked the command again, and approximately 5 s after that, I was dumped to SDDM. When I logged back in, I solely saw a black screen for 3 s. Then, DrKonqi appeared. However, as a screencast, that I shall upload after this, demonstrates, its QPalette is `breezedark` when focussed. However, it utilises Breeze Light when not focussed, as all other applications are, whether focused or not."


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGABRT
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=dba941;b=4d050e6f56ce4dc69628911d38860395;m=4760a3920;t=6432c41fc4dd8;x=36041a98c67a38c8
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.7-300.fc43.x86_64
package:        plasma-workspace-6.5.2-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        As https://bugs.kde.org/show_bug.cgi?id=511874#c0 explains, "Without any noticeable interaction from me, the sole visible panel hung. (I neglected to confirm whether the desktop was impacted, but I presume so.) To remediate this, I issued the "Log out" command via KRunner. This appeared to do nothing, so I repeated it. The sound for the first invocation played 15 s late, but I solely heard it once. 3 s after that, I invoked the command again, and approximately 5 s after that, I was dumped to SDDM. When I logged back in, I solely saw a black screen for 3 s. Then, DrKonqi appeared. However, as a screencast, that I shall upload after this, demonstrates, its QPalette is `breezedark` when focussed. However, it utilises Breeze Light when not focussed, as all other applications are, whether focused or not."
Comment 14 cherkaba 2025-11-09 19:48:15 UTC 
at session boot. i don't know how and why.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGSEGV
journald_cursor: s=8297339ffd124c1aa801d094d4bbd5f0;i=fe8bdb1;b=6ea58a7078d042cebea2b41fee6b5d98;m=1dfa6e0ef;t=6432b8a9512b7;x=82c382749262d814
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.7-300.fc43.x86_64
package:        plasma-workspace-6.5.2-1.fc43
runlevel:       /bin/sh: ligne 1: runlevel: commande introuvable
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        at session boot. i don't know how and why.
Comment 15 Igmar Palsenberg 2025-11-12 07:17:24 UTC 
Plugged in a USB-C to VGA converter, immediately unplugged it, and plugged it back in in a different port.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGSEGV
journald_cursor: s=8735c004deba4031829a1e0bc7eab936;i=ee2af;b=0383a5c7ffe34808b2935b63fa9d5b38;m=43bacca86;t=64356e57773b4;x=5d13acd3559927da
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.7-300.fc43.x86_64
package:        plasma-workspace-6.5.2-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        Plugged in a USB-C to VGA converter, immediately unplugged it, and plugged it back in in a different port.
Comment 16 Gregory Everitt 2025-11-12 17:30:23 UTC 
I closed the laptop to put it to sleep and I reopened it the next morning just to see a notification saying that plasmashell had crashed. I have not noticed any actual interruptions in functionality.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGABRT
journald_cursor: s=37fef4e936cc4c5782576b17bb44b699;i=98e80;b=db8d4b5a9c2b4d0e922ce5729d5f980c;m=158ffe44c;t=64367e753a7b4;x=7efa2f2683be97d1
executable:     /usr/bin/plasmashell
cmdline:        /usr/bin/plasmashell --no-respawn
rootdir:        /
uid:            1000
kernel:         6.17.7-300.fc43.x86_64
package:        plasma-workspace-6.5.2-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        I closed the laptop to put it to sleep and I reopened it the next morning just to see a notification saying that plasmashell had crashed. I have not noticed any actual interruptions in functionality.
Comment 17 cherkaba 2025-11-14 09:27:33 UTC 
plasma workplace crashed à boot time so i don't know why and how! but it occures several times , almost each time that à boot/restart my laptop. others crashes comes long with this one as kasts and krunner (not so frequent 1/8 times). i've already reported crashes ont kde.bugs platforme.


reporter:       libreport-2.17.15
type:           CCpp
reason:         krunner killed by SIGSEGV
journald_cursor: s=8297339ffd124c1aa801d094d4bbd5f0;i=1038368d;b=ab0481345ea74e4ca0ae95badbe9b958;m=7ac9ee0;t=643895efc0804;x=63453bbd91b74b8d
executable:     /usr/bin/krunner
cmdline:        /usr/bin/krunner --daemon
cgroup:         0::/user.slice/user-1000.slice/user/background.slice/plasma-krunner.service
rootdir:        /
uid:            1000
kernel:         6.17.7-300.fc43.x86_64
package:        plasma-workspace-6.5.2-1.fc43
runlevel:       /bin/sh: ligne 1: runlevel: commande introuvable
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        plasma workplace crashed à boot time so i don't know why and how! but it occures several times , almost each time that à boot/restart my laptop. others crashes comes long with this one as kasts and krunner (not so frequent 1/8 times). i've already reported crashes ont kde.bugs platforme.
Comment 18 Joshua 2025-11-18 11:03:56 UTC 
I added/removed the digital clocked widget


reporter:       libreport-2.17.15
crash_function: KCrash::defaultCrashHandler
backtrace_rating: 4
runlevel:       /bin/sh: line 1: runlevel: command not found
rootdir:        /
journald_cursor: s=3b4272de1da944d5bf7306dd1a29007c;i=3d1310c;b=e128b19c4e3d49518f39ddade7971127;m=1a90a9835;t=643dab3fbe315;x=a2506107718e76b8
type:           CCpp
uid:            1000
comment:        I added/removed the digital clocked widget
package:        plasma-workspace-6.5.2-1.fc43
cmdline:        /usr/bin/plasmashell --no-respawn
kernel:         6.17.7-300.fc43.x86_64
executable:     /usr/bin/plasmashell
reason:         plasmashell killed by SIGSEGV
Comment 19 Joshua 2025-11-23 09:36:54 UTC 
I added Individual CPU Core Usage widget on my desktop and attempted to configure it. This error seems to occur when I was navigating different settings of the said widget ("Line Chart Details", "Sensor Details", etc.).


reporter:       libreport-2.17.15
crash_function: KCrash::defaultCrashHandler
backtrace_rating: 4
runlevel:       /bin/sh: line 1: runlevel: command not found
rootdir:        /
journald_cursor: s=3b4272de1da944d5bf7306dd1a29007c;i=3d3c277;b=3f79e9585091422f83a328e9cb985d38;m=712136cf;t=6443f67c45c58;x=e4bc408d3104c750
type:           CCpp
uid:            1000
comment:        I added Individual CPU Core Usage widget on my desktop and attempted to configure it. This error seems to occur when I was navigating different settings of the said widget ("Line Chart Details", "Sensor Details", etc.).
package:        plasma-workspace-6.5.3-1.fc43
cmdline:        /usr/bin/plasmashell --no-respawn
kernel:         6.17.8-300.fc43.x86_64
executable:     /usr/bin/plasmashell
reason:         plasmashell killed by SIGSEGV
Comment 20 Joshua 2025-11-23 10:51:58 UTC 
Attempted to configure a desktop widget.


reporter:       libreport-2.17.15
crash_function: KCrash::defaultCrashHandler
backtrace_rating: 4
runlevel:       /bin/sh: line 1: runlevel: command not found
rootdir:        /
journald_cursor: s=3b4272de1da944d5bf7306dd1a29007c;i=3d3b645;b=3f79e9585091422f83a328e9cb985d38;m=61c0b4e2;t=6443f5863da6c;x=61675950080a7279
type:           CCpp
uid:            1000
comment:        Attempted to configure a desktop widget.
package:        plasma-workspace-6.5.3-1.fc43
cmdline:        /usr/bin/plasmashell --no-respawn
kernel:         6.17.8-300.fc43.x86_64
executable:     /usr/bin/plasmashell
reason:         plasmashell killed by SIGSEGV
Comment 21 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-11-23 23:57:49 UTC 
Likely relates to https://bugzilla.redhat.com/show_bug.cgi?id=2416610#c16.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGSEGV
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=e5c96f;b=11c385eff99444d2af4c4db3b5f573bf;m=3de3b3f85;t=6444b653d1eea;x=976e70b03dff495
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
comment:        Likely relates to https://bugzilla.redhat.com/show_bug.cgi?id=2416610#c16.
Comment 22 Ryan 2025-11-28 11:45:37 UTC 
opened firefox in X11 session, browsed to a livestream website, whole desktop crashed, can't use abrt because my api key doesn't let me report bugs apparently, but it claims this is a duplicate bug
Comment 23 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-11-28 15:15:01 UTC 
(In reply to Ryan from comment #22)

> desktop crashed, can't use abrt because my api key doesn't let me report
> bugs apparently, but it claims this is a duplicate bug

Generate a new key at https://bugzilla.redhat.com/userprefs.cgi?tab=apikey, then do as https://github.com/abrt/abrt/issues/1678#issuecomment-3541580497 advises.
Comment 24 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-12-09 15:19:42 UTC 
Occurred when I `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`'d, due to creating new tabs with QTerminal hanging PlasmaShell.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGSEGV
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=ef59b6;b=86995db4e1c54d5b9cac37656abbfaee;m=1ca4a4728;t=64585b5fe5d1b;x=79dcf13e84d22be5
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.9-300.fc43.x86_64
package:        plasma-workspace-6.5.3-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        Occurred when I `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`'d, due to creating new tabs with QTerminal hanging PlasmaShell.
Comment 25 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-12-21 00:59:58 UTC 
This occurred when https://community.gaijin.net/issues/p/warthunder/i/7q7ULF6XmD0a did.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGSEGV
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=fe2516;b=ff9d28b979e14a719b8a425543f3103f;m=5bf96172b;t=6466aef9dff2b;x=58a1a6832f29b4ab
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.12-300.fc43.x86_64
package:        plasma-workspace-6.5.4-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        This occurred when https://community.gaijin.net/issues/p/warthunder/i/7q7ULF6XmD0a did.
Comment 26 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-12-21 01:03:13 UTC 
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #25)

Submitted to https://bugs.kde.org/show_bug.cgi?id=513631#c0.
Comment 27 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-12-21 17:31:40 UTC 
Upon reproducing https://bugs.kde.org/show_bug.cgi?id=513197#c4, PlasmaShell hung [^1] longer than it otherwise would, at a lower maximum `ulimit -n` count. [^2] To remediate this, I invoked `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`. Upon login via SDDM, Konqi and GNOME Abrt appeared.

[^1]: https://github.com/lxqt/qterminal/issues/1309#issue-3711878851

[^2]: https://bugzilla.redhat.com/show_bug.cgi?id=2411800#c24


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGABRT
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=ff1ac1;b=5501e35729ce41878e5f237069022819;m=4618cad55;t=64678c58b6708;x=467521dbffae77f8
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.12-300.fc43.x86_64
package:        plasma-workspace-6.5.4-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
Comment 28 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-12-24 16:52:13 UTC 
I did as https://bugzilla.redhat.com/show_bug.cgi?id=2417691#c13 describes.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGSEGV
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=102c5a5;b=7768340840f0497788dd30f19b7bf62c;m=1875c5cbe;t=646b522937e11;x=f9e4dfb124c2cee7
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.12-300.fc43.x86_64
package:        plasma-workspace-6.5.4-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        I did as https://bugzilla.redhat.com/show_bug.cgi?id=2417691#c13 describes.
Comment 29 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-12-31 22:34:38 UTC 
As was stated in https://bugs.kde.org/show_bug.cgi?id=514016#c0, "When playing https://steamdb.info/depot/236391/history/?changeid=M:8993648880144243669", PlasmaShell SegV'd.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGSEGV
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=10ab980;b=7b842d190e1a47f2a5d751d411063031;m=1429e64e;t=64741fe872480;x=318f12380702fa7c
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.12-300.fc43.x86_64
package:        plasma-workspace-6.5.4-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        As was stated in https://bugs.kde.org/show_bug.cgi?id=514016#c0, "When playing https://steamdb.info/depot/236391/history/?changeid=M:8993648880144243669", PlasmaShell SegV'd.