Bug 462706

Summary: Since updating to 5.100 kded segfaults in Packagekit (likely during update check)
Product: [Applications] apper Reporter: Claudius <claudius+kde>
Component: generalAssignee: Daniel Nicoletti <dantti12>
Status: RESOLVED UPSTREAM    
Severity: crash CC: bernhardu, kdelibs-bugs, navarrums, nicolas.fella, smitha, tysontanx, ybx332
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Apper causes KDED to crash after login

Description Claudius 2022-12-06 13:26:58 UTC
SUMMARY
Konqi reports a crash in the tray after login. Updates notification does not appear.
I have not experienced any other problems during daily use however.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.11-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor
Memory: 15.5 GiB of RAM

ADDITIONAL INFORMATION

Backtrace:
Application: kded5 (kded5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>}
[KCrash Handler]
#6  0x00007f854a888828 in PackageKit::Transaction::role() const () at /usr/lib/libpackagekitqt5.so.1
#7  0x00007f854bf1450e in TransactionWatcher::watchTransaction(QDBusObjectPath const&, bool) (this=this@entry=0x55f791044070, tid=..., interactive=interactive@entry=false) at /usr/src/debug/apper-1.0.0/apperd/TransactionWatcher.cpp:104
#8  0x00007f854bf1478f in TransactionWatcher::transactionListChanged(QStringList const&) (this=0x55f791044070, tids=<optimized out>) at /usr/src/debug/apper-1.0.0/apperd/TransactionWatcher.cpp:85
#9  0x00007f85c28bda51 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff9194c420, r=<optimized out>, this=0x7f85b8068460, this=<optimized out>, r=<optimized out>, a=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#10 doActivate<false>(QObject*, int, void**) (sender=0x55f791042890, signal_index=8, argv=0x7fff9194c420) at kernel/qobject.cpp:3919
#11 0x00007f854a87caba in PackageKit::Daemon::transactionListChanged(QStringList const&) () at /usr/lib/libpackagekitqt5.so.1
#12 0x00007f85c28bdc00 in doActivate<false>(QObject*, int, void**) (sender=0x55f791042790, signal_index=5, argv=0x7fff9194c570) at kernel/qobject.cpp:3931
#13 0x00007f854a8953a9 in  () at /usr/lib/libpackagekitqt5.so.1
#14 0x00007f854a896393 in  () at /usr/lib/libpackagekitqt5.so.1
#15 0x00007f85c3b4845f in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector<int> const&, int) [clone .constprop.0] (this=<optimized out>, object=<optimized out>, msg=<optimized out>, metaTypes=<optimized out>, slotIdx=<optimized out>) at /usr/src/debug/qt5-base/qtbase/src/dbus/qdbusintegrator.cpp:1001
#16 0x00007f85c28b0be0 in QObject::event(QEvent*) (this=0x55f791042790, e=0x7f85b8068310) at kernel/qobject.cpp:1347
#17 0x00007f85c3578b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x55f791042790, e=0x7f85b8068310) at kernel/qapplication.cpp:3637
#18 0x00007f85c288cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55f791042790, event=0x7f85b8068310) at kernel/qcoreapplication.cpp:1064
#19 0x00007f85c288daa3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55f790607f00) at kernel/qcoreapplication.cpp:1821
#20 0x00007f85c28d3e68 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55f7907f5860) at kernel/qeventdispatcher_glib.cpp:277
#21 0x00007f85c171687b in g_main_dispatch (context=0x7f85b8005010) at ../glib/glib/gmain.c:3444
#22 g_main_context_dispatch (context=0x7f85b8005010) at ../glib/glib/gmain.c:4162
#23 0x00007f85c176d299 in g_main_context_iterate.constprop.0 (context=0x7f85b8005010, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4238
#24 0x00007f85c1715132 in g_main_context_iteration (context=0x7f85b8005010, may_block=1) at ../glib/glib/gmain.c:4303
#25 0x00007f85c28d7c4c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55f7907f6690, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#26 0x00007f85c288573c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7fff9194cb90, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#27 0x00007f85c2890269 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#28 0x00007f85c2d3a112 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1870
#29 0x00007f85c3576f2a in QApplication::exec() () at kernel/qapplication.cpp:2829
#30 0x000055f78e833040 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kded/kded-5.100.0/src/kded.cpp:770
[Inferior 1 (process 1116) detached]
Comment 1 Antonio Rojas 2022-12-06 15:14:07 UTC
The crash is in packagekit-qt and unrelated to kded, please report it upstream at https://github.com/PackageKit/PackageKit-Qt
Comment 2 Nicolas Fella 2022-12-06 15:25:18 UTC
Could also be a problem with appear, but either way, not a bug in the kded framework
Comment 3 Bernhard Übelacker 2023-01-04 10:38:59 UTC
I tried to bring this to the attention of packagekit-qt
developers in this bug report:
  https://github.com/PackageKit/PackageKit-Qt/issues/42
Comment 4 Claudius 2023-01-05 01:55:32 UTC
(In reply to Bernhard Übelacker from comment #3)
> I tried to bring this to the attention of packagekit-qt
Thank you! I didn't have the time to report it to upstream yet.
It also doesn't seem to happen every time.  
It might be some sort of race condition.
Comment 5 Tyson Tan 2023-01-09 12:11:44 UTC
Created attachment 155131 [details]
Apper causes KDED to crash after login

I've reported my information to https://github.com/PackageKit/PackageKit-Qt/issues/42

But just in case, I will post those info here, as well.

This also happens to me but it's on Archlinux. Apper causes kded5 to crash at login. This bug began to happen since KDE Plasma 5.26.3 or .4, KDE Framework 5.100.0. It happens at every login, on multiple machines, all of them ArchLinux.

The crash would happen a few seconds after I logged in to KDE Plasma Desktop. The whole desktop would appears to freeze for a few seconds. KDE Crash Handler would then notify me about kded5 crashed. But when I click the button to see Developer Information, the Crash Handler would also crash. KDED would not restart automatically after that.

I thought it could have been Apper/packagekit-qt's automatic update checker not compatible with the newer KDE components, but I could not stop KDED from crashing even after I disabled every automatic update function in Apper. The only way was to uninstall Apper from the system (I didn't need to uninstall packagekit or packagekit-qt5).

BTW, all my machines has a Intel CPU. So I don't think this is Zen4 specific?

Following is the crash information from DrKonqi.
Comment 6 Nicolas Fella 2023-01-11 17:45:02 UTC
*** Bug 463576 has been marked as a duplicate of this bug. ***
Comment 7 mozo 2023-01-13 13:07:28 UTC
(In reply to Tyson Tan from comment #5)
> Created attachment 155131 [details]
> Apper causes KDED to crash after login
> 
> I've reported my information to
> https://github.com/PackageKit/PackageKit-Qt/issues/42
> 
> But just in case, I will post those info here, as well.
> 
> This also happens to me but it's on Archlinux. Apper causes kded5 to crash
> at login. This bug began to happen since KDE Plasma 5.26.3 or .4, KDE
> Framework 5.100.0. It happens at every login, on multiple machines, all of
> them ArchLinux.
> 
> The crash would happen a few seconds after I logged in to KDE Plasma
> Desktop. The whole desktop would appears to freeze for a few seconds. KDE
> Crash Handler would then notify me about kded5 crashed. But when I click the
> button to see Developer Information, the Crash Handler would also crash.
> KDED would not restart automatically after that.
> 
> I thought it could have been Apper/packagekit-qt's automatic update checker
> not compatible with the newer KDE components, but I could not stop KDED from
> crashing even after I disabled every automatic update function in Apper. The
> only way was to uninstall Apper from the system (I didn't need to uninstall
> packagekit or packagekit-qt5).
> 
> BTW, all my machines has a Intel CPU. So I don't think this is Zen4 specific?
> 
> Following is the crash information from DrKonqi.

Same here on Arch Linux and was wondering what's the problem, thanks! I'll uninstall Apper and let's hope this will fix it.
Comment 8 Nicolas Fella 2023-01-28 11:14:24 UTC
*** Bug 464934 has been marked as a duplicate of this bug. ***