Bug 467027 - Discover crashes in PKResultsStream::sendResources() on startup while feching updates
Summary: Discover crashes in PKResultsStream::sendResources() on startup while feching...
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: PackageKit (other bugs)
Version First Reported In: 5.27.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
: 469614 481547 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-03-07 19:58 UTC by Dimitar Petrovski
Modified: 2025-05-12 03:46 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitar Petrovski 2023-03-07 19:58:21 UTC
Application: plasma-discover (5.27.2)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.2.2-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.2 [KCrashBackend]

-- Information about the crash:
I constatnly get a crash when starting while fetching updates, I have tried online and offline

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>}
[KCrash Handler]
#6  std::__atomic_base<QObjectPrivate::SignalVector*>::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x28) at /usr/include/c++/12.2.1/atomic:578
#7  std::atomic<QObjectPrivate::SignalVector*>::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x28) at /usr/include/c++/12.2.1/atomic:579
#8  QAtomicOps<QObjectPrivate::SignalVector*>::loadRelaxed<QObjectPrivate::SignalVector*>(std::atomic<QObjectPrivate::SignalVector*> const&) (_q_value=<error reading variable: Cannot access memory at address 0x28>) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#9  QBasicAtomicPointer<QObjectPrivate::SignalVector>::loadRelaxed() const (this=0x28) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#10 QObjectPrivate::maybeSignalConnected(unsigned int) const (this=0x7faa24130140, signalIndex=3) at kernel/qobject.cpp:500
#11 0x00007faac80be75f in doActivate<false>(QObject*, int, void**) (sender=0x55d309654330, signal_index=3, argv=0x7fffffe19050) at kernel/qobject.cpp:3825
#12 0x00007faaca1ce9d7 in ResultsStream::resourcesFound(QVector<AbstractResource*> const&) (this=this@entry=0x55d309654330, _t1=...) at /usr/src/debug/discover/build/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:159
#13 0x00007faa751890ca in PKResultsStream::sendResources(QVector<AbstractResource*> const&, bool) (this=0x55d309654330, res=..., waitForResolved=<optimized out>) at /usr/src/debug/discover/discover-5.27.2/libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp:542
#14 0x00007faa7518d5be in operator() (__closure=0x55d30c32dda0) at /usr/src/debug/discover/discover-5.27.2/libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp:635
#15 std::__invoke_impl<void, PackageKitBackend::search(const AbstractResourcesBackend::Filters&)::<lambda()>&> (__f=...) at /usr/include/c++/12.2.1/bits/invoke.h:61
#16 std::__invoke_r<void, PackageKitBackend::search(const AbstractResourcesBackend::Filters&)::<lambda()>&> (__fn=...) at /usr/include/c++/12.2.1/bits/invoke.h:111
#17 std::_Function_handler<void(), PackageKitBackend::search(const AbstractResourcesBackend::Filters&)::<lambda()> >::_M_invoke(const std::_Any_data &) (__functor=<optimized out>) at /usr/include/c++/12.2.1/bits/std_function.h:290
#18 0x00007faac80b1bb0 in QObject::event(QEvent*) (this=0x55d30880c000, e=0x7faa2400fe40) at kernel/qobject.cpp:1347
#19 0x00007faac9b78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x55d30880c000, e=0x7faa2400fe40) at kernel/qapplication.cpp:3640
#20 0x00007faac808df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55d30880c000, event=0x7faa2400fe40) at kernel/qcoreapplication.cpp:1064
#21 0x00007faac808dfb3 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1462
#22 0x00007faac808ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55d3081c3e10) at kernel/qcoreapplication.cpp:1821
#23 0x00007faac80d4e88 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55d3082cad70) at kernel/qeventdispatcher_glib.cpp:277
#24 0x00007faac6d1682b in g_main_dispatch (context=0x7faabc005010) at ../glib/glib/gmain.c:3454
#25 g_main_context_dispatch (context=0x7faabc005010) at ../glib/glib/gmain.c:4172
#26 0x00007faac6d6dcc9 in g_main_context_iterate.constprop.0 (context=0x7faabc005010, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4248
#27 0x00007faac6d150e2 in g_main_context_iteration (context=0x7faabc005010, may_block=1) at ../glib/glib/gmain.c:4313
#28 0x00007faac80d8c6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55d3082cbc10, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x00007faac80866ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7fffffe19600, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#30 0x00007faac8091219 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#31 0x00007faac8539fe2 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1870
#32 0x00007faac9b76f2a in QApplication::exec() () at kernel/qapplication.cpp:2832
#33 0x000055d30651f947 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/discover/discover-5.27.2/discover/main.cpp:224
[Inferior 1 (process 11871) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2023-03-13 17:04:59 UTC

*** This bug has been marked as a duplicate of bug 466955 ***
Comment 2 Nate Graham 2023-05-15 19:11:17 UTC

*** This bug has been marked as a duplicate of bug 463864 ***
Comment 3 Nate Graham 2023-05-15 19:13:55 UTC
*** Bug 469614 has been marked as a duplicate of this bug. ***
Comment 4 Nicolas Fella 2024-02-20 13:32:57 UTC
*** Bug 481547 has been marked as a duplicate of this bug. ***
Comment 5 Aleix Pol 2025-04-12 17:08:07 UTC
Seems like an issue that has been addressed, do you still have this issue?
Comment 6 Bug Janitor Service 2025-04-27 03:47:20 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2025-05-12 03:46:58 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.