Bug 2376518 - [abrt] plasma-workspace: KCrash::defaultCrashHandler(): plasmashell killed by SIGABRT
Summary: [abrt] plasma-workspace: KCrash::defaultCrashHandler(): plasmashell killed by...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 42
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:c6d3b9334769a856908192d5818...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-05 16:32 UTC by Mr Beedell, Roke Julian Lockhart
Modified: 2026-05-09 01:42 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-05-09 01:42:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.49 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: maps (3.87 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: limits (1.29 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: environ (2.65 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: open_fds (15.32 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: mountinfo (4.00 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: os_info (767 bytes, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: cpuinfo (3.55 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: core_backtrace (217.33 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: var_log_messages (307 bytes, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details
File: backtrace (112.02 KB, text/plain)
2025-07-05 16:32 UTC, Mr Beedell, Roke Julian Lockhart
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 507936 0 NOR UNCONFIRMED [ANR] PlasmaShell hung soon after login 2025-08-06 11:16:49 UTC
Red Hat Bugzilla 2366684 0 unspecified CLOSED [abrt] plasma-drkonqi: qAbort(): drkonqi killed by SIGABRT 2026-06-08 17:11:10 UTC
Red Hat Bugzilla 2376516 0 unspecified CLOSED [abrt] plasma-workspace: allocateData(): plasmashell killed by SIGABRT 2026-05-09 02:12:57 UTC
Red Hat Bugzilla 2376518 0 unspecified CLOSED [abrt] plasma-workspace: KCrash::defaultCrashHandler(): plasmashell killed by SIGABRT 2026-05-09 01:42:47 UTC
freedesktop.org Gitlab mesa/mesa/-/work_items/14257 0 None None None 2026-05-09 01:42:47 UTC

Internal Links: 2376516 2376518

Description Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:27 UTC
Description of problem:
This occurred at the same time that https://bugzilla.redhat.com/show_bug.cgi?id=2366684#c15 did, whose description is "Very soon after reporting https://bugzilla.redhat.com/show_bug.cgi?id=2376516, `plasmashell` indefinitely hung. I left it for 20s, then invoked `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`."

Version-Release number of selected component:
plasma-workspace-6.4.1-2.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGABRT
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=80e0a6;b=883863934c534a93ac2e371b83550dbf;m=1cb98c4bd;t=63930f06210f4;x=70c0b8800638897b
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.15.4-200.fc42.x86_64
package:        plasma-workspace-6.4.1-2.fc42
runlevel:       N 5
dso_list:       /usr/bin/plasmashell plasma-workspace-6.4.1-2.fc42.x86_64 (Fedora Project) 1751156429
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        This occurred at the same time that https://bugzilla.redhat.com/show_bug.cgi?id=2366684#c15 did, whose description is "Very soon after reporting https://bugzilla.redhat.com/show_bug.cgi?id=2376516, `plasmashell` indefinitely hung. I left it for 20s, then invoked `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`."

Truncated backtrace:
Thread no. 0 (38 frames)
 #3 KCrash::defaultCrashHandler at /usr/src/debug/kf6-kcrash-6.15.0-1.fc42.x86_64/src/kcrash.cpp:605
 #5 syscall at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
 #6 sys_futex at ../src/util/futex.c:43
 #7 futex_wait at ../src/util/futex.c:55
 #8 do_futex_fence_wait at ../src/util/u_queue.c:131
 #9 _util_queue_fence_wait at ../src/util/u_queue.c:146
 #10 util_queue_fence_wait at ../src/util/u_queue.h:181
 #12 util_queue_finish at ../src/util/u_queue.c:722
 #13 si_set_debug_callback at ../src/gallium/drivers/radeonsi/si_pipe.c:447
 #14 si_destroy_context at ../src/gallium/drivers/radeonsi/si_pipe.c:197
 #15 tc_destroy at ../src/gallium/auxiliary/util/u_threaded_context.c:5183
 #16 st_destroy_context_priv at ../src/mesa/state_tracker/st_context.c:358
 #17 st_destroy_context at ../src/mesa/state_tracker/st_context.c:976
 #18 dri_destroy_context at ../src/gallium/frontends/dri/dri_context.c:280
 #19 driDestroyContext at ../src/gallium/frontends/dri/dri_util.c:639
 #20 dri2_destroy_context at ../src/egl/drivers/dri2/egl_dri2.c:1307
 #22 eglDestroyContext at ../src/egl/main/eglapi.c:930
 #23 QtWaylandClient::QWaylandGLContext::~QWaylandGLContext at /usr/src/debug/qt6-qtwayland-6.9.1-3.fc42.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:299
 #25 QOpenGLContext::destroy at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qopenglcontext.cpp:461
 #26 QOpenGLContext::~QOpenGLContext at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qopenglcontext.cpp:488
 #27 QRhiGles2InitParams::newFallbackSurface at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/rhi/qrhigles2.cpp:604
 #28 QSGRhiSupport::maybeCreateOffscreenSurface at /usr/src/debug/qt6-qtdeclarative-6.9.1-2.fc42.x86_64/src/quick/scenegraph/qsgrhisupport.cpp:901
 #30 QSGThreadedRenderLoop::handleExposure at /usr/src/debug/qt6-qtdeclarative-6.9.1-2.fc42.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1314
 #31 QWindow::event at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qwindow.cpp:2742
 #32 QApplicationPrivate::notify_helper at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/widgets/kernel/qapplication.cpp:3303
 #33 QCoreApplication::notifyInternal2 at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1106
 #34 QCoreApplication::sendSpontaneousEvent at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1560
 #35 QGuiApplicationPrivate::processExposeEvent at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:3480
 #36 QWindowSystemInterface::sendWindowSystemEvents at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qwindowsysteminterface.cpp:1113
 #37 QWindowSystemInterface::flushWindowSystemEvents at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qwindowsysteminterface.cpp:1082
 #38 doActivate<false> at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4158
 #39 QMetaObject::activate at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4206
 #40 QAbstractEventDispatcher::awake at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/redhat-linux-build/src/corelib/Core_autogen/include/moc_qabstracteventdispatcher.cpp:128
 #41 QEventDispatcherGlib::processEvents at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:406
 #42 QEventLoop::exec at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/global/qflags.h:77
 #43 QCoreApplication::exec at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1449
 #44 QGuiApplication::exec at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1986
 #45 QApplication::exec at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/widgets/kernel/qapplication.cpp:2570

Comment 1 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:31 UTC
Created attachment 2096199 [details]
File: proc_pid_status

Comment 2 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:32 UTC
Created attachment 2096200 [details]
File: maps

Comment 3 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:34 UTC
Created attachment 2096201 [details]
File: limits

Comment 4 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:35 UTC
Created attachment 2096202 [details]
File: environ

Comment 5 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:36 UTC
Created attachment 2096203 [details]
File: open_fds

Comment 6 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:37 UTC
Created attachment 2096204 [details]
File: mountinfo

Comment 7 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:38 UTC
Created attachment 2096205 [details]
File: os_info

Comment 8 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:39 UTC
Created attachment 2096206 [details]
File: cpuinfo

Comment 9 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:41 UTC
Created attachment 2096207 [details]
File: core_backtrace

Comment 10 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:42 UTC
Created attachment 2096208 [details]
File: var_log_messages

Comment 11 Mr Beedell, Roke Julian Lockhart 2025-07-05 16:32:43 UTC
Created attachment 2096209 [details]
File: backtrace

Comment 12 Mr Beedell, Roke Julian Lockhart 2025-08-06 11:15:07 UTC
Soon after log in, as I transferred some files from KDE Connect, Plasma Shell hung. When I logged out via KRunner, the DE offered to kill it so that I would be able to log out.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGABRT
journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=1df063;b=c4dc730b422544769b93da50285be40a;m=54d60ec;t=63bb02300f0db;x=54ec2320ab3dc9eb
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.15.8-200.fc42.x86_64
package:        plasma-workspace-6.4.3-1.fc42
runlevel:       N 5
dso_list:       /usr/bin/plasmashell plasma-workspace-6.4.3-1.fc42.x86_64 (Fedora Project) 1752933773
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        Soon after log in, as I transferred some files from KDE Connect, Plasma Shell hung. When I logged out via KRunner, the DE offered to kill it so that I would be able to log out.

Comment 13 Mr Beedell, Roke Julian Lockhart 2025-08-06 11:16:49 UTC
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #12)

Reported upstream, at https://bugs.kde.org/show_bug.cgi?id=507936#c0.

Comment 14 Alan 2025-08-09 16:01:51 UTC
I entered configuration mode on the panel, and it immediately become unresponsive. I didn't have access to Application Launcher as a result of this behavior, but I had Firefox running and was still able to use it.. I launched the terminal via Ctrl-Alt-T and ran `loginctl  terminate-user`. I tried to log in again switching back to Gnome Session, but it got stuck. I canceled login and restarted the computer.


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasmashell killed by SIGABRT
journald_cursor: s=03c94ab394a745278544e75326baf823;i=55aa5;b=c3d75f3ef8754befa3b465d72d30a431;m=84a43a5c3;t=63bf031bf58a9;x=d4cb8b6065f7ef0f
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.15.8-200.fc42.x86_64
package:        plasma-workspace-6.4.3-1.fc42
runlevel:       N 5
dso_list:       /usr/bin/plasmashell plasma-workspace-6.4.3-1.fc42.x86_64 (Fedora Project) 1753143359
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        I entered configuration mode on the panel, and it immediately become unresponsive. I didn't have access to Application Launcher as a result of this behavior, but I had Firefox running and was still able to use it.. I launched the terminal via Ctrl-Alt-T and ran `loginctl  terminate-user`. I tried to log in again switching back to Gnome Session, but it got stuck. I canceled login and restarted the computer.

Comment 15 Fedora Release Engineering 2026-05-06 13:27:53 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.


Note You need to log in before you can comment on or make changes to this bug.