Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: When I posted https://sourceforge.net/p/opencamera/discussion/general/thread/a0f4c96a60/?limit=25#3ccd/66b0:~:text=Thanks%20for%20the%20effort%2C%20@Anonymous%2C%20but%20that's%20a%20little%20unactionably%20nondescript, I encountered https://crash-stats.mozilla.org/report/index/d1d96a33-e4a3-433d-b866-24f750250802#:~:text=Crash%20Report%20%5B@%20__syscall_cancel_arch%20%5D. Whilst the crash reporter was visible, I invoked `gnome-abrt-1.4.3-4.fc42.x86_64`, via the Task Manager plasmoid. This hung the shell, so I invoked `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`. This killed the shell, because it was non-responsive. Version-Release number of selected component: kactivitymanagerd-6.4.3-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: kactivitymanagerd killed by SIGABRT journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=1cbfcc;b=5f07eb01675f4c0ebd0e6f0a0cf4b60c;m=b6d67ddee;t=63b699682096e;x=f6770e6f28b8c647 executable: /usr/libexec/kactivitymanagerd cmdline: /usr/libexec/kactivitymanagerd cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-kactivitymanagerd.service rootdir: / uid: 1000 kernel: 6.15.8-200.fc42.x86_64 package: kactivitymanagerd-6.4.3-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: When I posted https://sourceforge.net/p/opencamera/discussion/general/thread/a0f4c96a60/?limit=25#3ccd/66b0:~:text=Thanks%20for%20the%20effort%2C%20@Anonymous%2C%20but%20that's%20a%20little%20unactionably%20nondescript, I encountered https://crash-stats.mozilla.org/report/index/d1d96a33-e4a3-433d-b866-24f750250802#:~:text=Crash%20Report%20%5B@%20__syscall_cancel_arch%20%5D. Whilst the crash reporter was visible, I invoked `gnome-abrt-1.4.3-4.fc42.x86_64`, via the Task Manager plasmoid. This hung the shell, so I invoked `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`. This killed the shell, because it was non-responsive. Truncated backtrace: Thread no. 1 (11 frames) #4 qAbort at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/global/qassert.cpp:46 #5 qt_message_fatal<QString&> at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/global/qlogging.cpp:2122 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/global/qlogging.cpp:381 #7 QMessageLogger::fatal at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/global/qlogging.cpp:883 #8 init_platform at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1345 #9 QGuiApplicationPrivate::createPlatformIntegration at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1591 #10 QGuiApplicationPrivate::createEventDispatcher at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1610 #11 QCoreApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:866 #12 QGuiApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1638 #13 QGuiApplication::QGuiApplication at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.h:172 #14 Application::Application at /usr/src/debug/kactivitymanagerd-6.4.3-1.fc42.x86_64/src/service/Application.cpp:105
Created attachment 2102567 [details] File: proc_pid_status
Created attachment 2102568 [details] File: maps
Created attachment 2102569 [details] File: limits
Created attachment 2102570 [details] File: environ
Created attachment 2102571 [details] File: open_fds
Created attachment 2102572 [details] File: mountinfo
Created attachment 2102573 [details] File: os_info
Created attachment 2102574 [details] File: cpuinfo
Created attachment 2102575 [details] File: core_backtrace
Created attachment 2102576 [details] File: dso_list
Created attachment 2102577 [details] File: backtrace
https://bugzilla.redhat.com/show_bug.cgi?id=2367146#c15 occurred when this did, although that's expected, and mostly irrelevant.
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.
As https://bugzilla.mozilla.org/show_bug.cgi?id=978792#c5 explains, this is nigh undisagnosable, I presume.