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
Created attachment 2111872 [details] File: proc_pid_status
Created attachment 2111873 [details] File: maps
Created attachment 2111874 [details] File: limits
Created attachment 2111875 [details] File: open_fds
Created attachment 2111876 [details] File: mountinfo
Created attachment 2111877 [details] File: os_info
Created attachment 2111878 [details] File: cpuinfo
Created attachment 2111879 [details] File: core_backtrace
Created attachment 2111880 [details] File: dso_list
Created attachment 2111881 [details] File: var_log_messages
Created attachment 2111882 [details] File: backtrace
Created attachment 2111883 [details] File: environ
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."
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.
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.
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.
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.
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
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
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
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.
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
(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.
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.
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.
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #25) Submitted to https://bugs.kde.org/show_bug.cgi?id=513631#c0.
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
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.
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.
As at https://bugs.kde.org/show_bug.cgi?id=514353#c0, "I do not know what caused this, but it occurred when I switched tabs in Firefox." reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=113d1c4;b=4c99550dd6b54ef88178f7efbd0fc7ce;m=7e5b694d9;t=647e8dd6440d3;x=fbb16e9b1a346460 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 at https://bugs.kde.org/show_bug.cgi?id=514353#c0, "I do not know what caused this, but it occurred when I switched tabs in Firefox."
I use Koi software which switches light/dark Plasma theme based on time. When Koi switches theme from light to dark, the crash usually happens. reporter: libreport-2.17.15 type: CCpp reason: krunner killed by SIGSEGV journald_cursor: s=104094575bef4447a81f3b0e05d97a16;i=d30607;b=718d3d9994544e5f8bf92926d8025460;m=5347f6f419;t=64815a17d8bf7;x=6efd72d047eb2d71 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.12-300.fc43.x86_64 package: plasma-workspace-6.5.4-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found xsession_errors: backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler
When I `qdbus-qt6 org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`'d (via `plasmashell`), I re-authenticated via SDDM. This took me to a black screen for > 30 s, after which I observed a multitude of Abrt and Konqi crash logs, of which one of them was for the Konqi wizard. < 15 s afterward, I was forcefully exited from the session, and taken to a black screen, whereupon my monitor disconnected. Using Control + Alt + F3/F4, I was able to access my session again. This is not the first time that this has occurred. reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=11922ea;b=4c4bf61e1c584f5f85e90202510daf11;m=10779640f;t=6486c72ded895;x=43809a4d433ea703 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.18.4-200.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
With: > ~~~yaml > ID: com.hypixel.HytaleLauncher > Ref: app/com.hypixel.HytaleLauncher/x86_64/master > Arch: x86_64 > Branch: master > License: LicenseRef-proprietary > Origin: hytalelauncher-origin > Collection: > Installation: system > Installed: 23.5 MB > Runtime: org.gnome.Platform/x86_64/48 > Sdk: org.gnome.Sdk/x86_64/48 > > Commit: 3ec03d4f03eac4e617cccdd52604e16a9649ad5cd8e13715d27867767316a005 > Subject: Export com.hypixel.HytaleLauncher > Date: 2026-01-15 18:13:20 +0000 > ~~~ â¦using `2026.01.17-4b0f30090` on `release/2026.01.16-2e2291a`, when I entered the Windrunner portal, as a client on a LAN (UPnP) server, my allowed time there elapsed. Although the host was able to return, Hytale merely displayed `#000000` thereafter, and it did not respond to `kdotool windowclose $(kdotool getactivewindow)`, nor even `qdbus-qt6 org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`. Solely `qdbus-qt6 org.kde.LogoutPrompt /LogoutPrompt promptReboot` did. reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=11c5798;b=037c2379d19a4cffa0b52880c56efcee;m=ae8e0743;t=648a6b72ea161;x=da6e797f61544f46 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.18.5-200.fc43.x86_64 package: plasma-workspace-6.5.5-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler
As reported upstream, at https://bugs.kde.org/show_bug.cgi?id=514998#c0: "After applying updates via `flatpak update -y && sudo dnf5 upgrade -y --refresh --offline && sudo dnf5 offline reboot -y`, with automatic login upon boot enabled, PlasmaShell SegV'd. I was not at my desktop when it occurred, but returned only a minute after it ocurred, so I know that it was at the time of login." reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGSEGV journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=1260f04;b=fe55080344654deab9a35f0fcc57254a;m=1763ad4;t=64916b94d4b62;x=8604d0d9a0ed5702 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.18.5-200.fc43.x86_64 package: plasma-workspace-6.5.5-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler comment: As reported upstream, at https://bugs.kde.org/show_bug.cgi?id=514998#c0: "After applying updates via `flatpak update -y && sudo dnf5 upgrade -y --refresh --offline && sudo dnf5 offline reboot -y`, with automatic login upon boot enabled, PlasmaShell SegV'd. I was not at my desktop when it occurred, but returned only a minute after it ocurred, so I know that it was at the time of login."
crashed after my displays went to sleep reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGABRT journald_cursor: s=7a8ffd3eade149eda93ac770b8403ca4;i=65682d;b=59eae91447e44eceb8fbcfb293d88b89;m=dade4c2c;t=64986434f152a;x=37d315eb2d0586a7 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.18.7-200.fc43.x86_64 package: plasma-workspace-6.5.5-1.fc43 runlevel: /bin/sh: linha 1: runlevel: comando não encontrado backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler comment: crashed after my displays went to sleep
I did as https://bugs.kde.org/show_bug.cgi?id=515261#c0 describes. reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGSEGV journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=12b08f0;b=31ebc03eaa6a40be9b3d7fa179f918c5;m=171be1b;t=6498600500a00;x=b009719ad9fde9df 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.18.6-200.fc43.x86_64 package: plasma-workspace-6.5.5-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: KCrash::defaultCrashHandler comment: I did as https://bugs.kde.org/show_bug.cgi?id=515261#c0 describes.