Bug 506920 - A Counterpart Of 506919
Summary: A Counterpart Of 506919
Status: RESOLVED DUPLICATE of bug 506919
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 6.4.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-07-11 17:41 UTC by Roke Julian Lockhart Beedell
Modified: 2025-07-11 17:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (87.16 KB, text/plain)
2025-07-11 17:41 UTC, Roke Julian Lockhart Beedell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roke Julian Lockhart Beedell 2025-07-11 17:41:34 UTC
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<QMutexPrivate*>::load (this=0x79, __m=std::memory_order_relaxed) at /usr/include/c++/15/bits/atomic_base.h:828
#6  std::atomic<QMutexPrivate*>::load (this=0x79, __m=std::memory_order_relaxed) at /usr/include/c++/15/atomic:587
#7  QAtomicOps<QMutexPrivate*>::loadRelaxed<QMutexPrivate*> (_q_value=<error reading variable: Cannot access memory at address 0x79>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qatomic_cxx11.h:202
#8  QBasicAtomicPointer<QMutexPrivate>::loadRelaxed (this=0x79) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qbasicatomic.h:170
#9  QBasicMutex::fastTryLock (this=0x79) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qmutex.h:80
#10 QBasicMutex::lock (this=0x79) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qmutex.h:43
#11 std::unique_lock<QMutex>::lock (this=<synthetic pointer>) at /usr/include/c++/15/bits/unique_lock.h:144
#12 std::unique_lock<QMutex>::unique_lock (this=<synthetic pointer>, __m=...) at /usr/include/c++/15/bits/unique_lock.h:75
#13 (anonymous namespace)::qt_unique_lock<QMutex> (mutex=...) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qlocking_p.h:66
#14 QCoreApplicationPrivate::lockThreadPostEventList (object=object@entry=0x5585a3290eb0) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1586
#15 0x00007f499cf52ff3 in QObject::deleteLater (this=0x5585a3290eb0) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:2457
#16 0x00007f499cf657ba in QtPrivate::QSlotObjectBase::call (this=0x5585a32a6890, r=0x5585a3290eb0, a=0x7ffc70090bc0) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461
#17 doActivate<false> (sender=0x5585a27fb1a0, signal_index=5, argv=argv@entry=0x7ffc70090bc0) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4146
[...]
#20 AbstractBackendUpdater::progressingChanged (this=this@entry=0x5585a27fb1a0, _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
#21 0x00007f490759ced5 in PackageKitUpdater::setProgressing (this=0x5585a27fb1a0, progressing=false) at /usr/src/debug/plasma-discover-6.4.2-1.fc42.x86_64/libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp:783
#22 PackageKitUpdater::setProgressing (this=0x5585a27fb1a0, progressing=false) at /usr/src/debug/plasma-discover-6.4.2-1.fc42.x86_64/libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp:779


Reported using DrKonqi
Comment 1 Roke Julian Lockhart Beedell 2025-07-11 17:41:35 UTC
Created attachment 183166 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Roke Julian Lockhart Beedell 2025-07-11 17:42:21 UTC

*** This bug has been marked as a duplicate of bug 506919 ***