Application: plasma-discover (6.4.2) ApplicationNotResponding [ANR]: false Qt Version: 6.9.1 Frameworks Version: 6.15.0 Operating System: Linux 6.15.4-200.fc42.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 42 (KDE Plasma Desktop Edition)" DrKonqi: 6.4.2 [CoredumpBackend] -- Information about the crash: This occurred when https://bugs.kde.org/show_bug.cgi?id=506919 did. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 std::__atomic_base<QThreadData*>::load (this=0xe9530398b658ce4d, __m=std::memory_order_acquire) at /usr/include/c++/15/bits/atomic_base.h:828 #6 std::atomic<QThreadData*>::load (this=0xe9530398b658ce4d, __m=std::memory_order_acquire) at /usr/include/c++/15/atomic:587 #7 QAtomicOps<QThreadData*>::loadAcquire<QThreadData*> (_q_value=<error reading variable: Cannot access memory at address 0xe9530398b658ce4d>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qatomic_cxx11.h:214 #8 QBasicAtomicPointer<QThreadData>::loadAcquire (this=0xe9530398b658ce4d) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qbasicatomic.h:177 #9 QCoreApplicationPrivate::lockThreadPostEventList (object=object@entry=0x555e71d1b530) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1580 #10 0x00007f5051f52ff3 in QObject::deleteLater (this=0x555e71d1b530) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:2457 #11 0x00007f5051f657ba in QtPrivate::QSlotObjectBase::call (this=0x555e71e2a710, r=0x555e71d1b530, a=0x7ffe22535a40) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461 #12 doActivate<false> (sender=0x555e7148e290, signal_index=5, argv=argv@entry=0x7ffe22535a40) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4146 [...] #15 AbstractBackendUpdater::progressingChanged (this=this@entry=0x555e7148e290, _t1=<optimized out>, _t1@entry=false) at /usr/src/debug/plasma-discover-6.4.2-1.fc42.x86_64/redhat-linux-build/libdiscover/DiscoverCommon_autogen/include/moc_AbstractBackendUpdater.cpp:305 #16 0x00007f4fcc56ced5 in PackageKitUpdater::setProgressing (this=0x555e7148e290, progressing=false) at /usr/src/debug/plasma-discover-6.4.2-1.fc42.x86_64/libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp:783 #17 PackageKitUpdater::setProgressing (this=0x555e7148e290, progressing=false) at /usr/src/debug/plasma-discover-6.4.2-1.fc42.x86_64/libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp:779 #18 PackageKitUpdater::finished (this=0x555e7148e290, exit=PackageKit::Transaction::ExitSuccess) at /usr/src/debug/plasma-discover-6.4.2-1.fc42.x86_64/libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp:615 #19 0x00007f5051f657ba in QtPrivate::QSlotObjectBase::call (this=0x555e71f95cf0, r=0x555e7148e290, a=0x7ffe22535de0) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461 #20 doActivate<false> (sender=0x555e71406e30, signal_index=23, argv=argv@entry=0x7ffe22535de0) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4146 [...] #22 0x00007f4fcc4bc5d8 in PackageKit::Transaction::finished (this=this@entry=0x555e71406e30, _t1=<optimized out>, _t2=<optimized out>) at /usr/src/debug/PackageKit-Qt-1.1.1-8.fc42.x86_64/pkqt6/redhat-linux-build/src/packagekitqt6_autogen/include/moc_transaction.cpp:1750 #23 0x00007f4fcc4c3df1 in PackageKit::TransactionPrivate::finished (this=0x555e72347d40, exitCode=<optimized out>, runtime=<optimized out>) at /usr/src/debug/PackageKit-Qt-1.1.1-8.fc42.x86_64/src/transactionprivate.cpp:243 Reported using DrKonqi
Created attachment 183167 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
*** This bug has been marked as a duplicate of bug 506919 ***
If you'd like to add additional backtrace events to a bug, a better way is to turn on Automatic reporting when Dr Konqi launches. Opening and closing duplicate bugs for the same crash only clutters up Bugzilla.
(In reply to TraceyC from comment #3) I can't access Sentry events, though, which means I can get kinda confused when I see multiple ABRT reports in RHBZ that don't correspond 1:1 to KDE BZ bugs. I thought it best to do this than accidentally repeat information that's already in sentry. I try not to report them unless I've reason to believe they differ, but perhaps ABRT considering them different isn't sufficient? Apologies regardless.