Version: 4.2.3 (using KDE 4.2.3) OS: Linux Installed from: Fedora RPMs Using Fedora 11, with updates-testing repo enabled, kded4 crash after some time on every login. Not sure what the cause is, seemingly it just happens after a couple of minutes of normal use. Application: KDE Daemon (kded4), signal SIGABRT 0x0000003a6b6a3e61 in nanosleep () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fe1285d3820 (LWP 2713))] Thread 2 (Thread 0x7fe11b247910 (LWP 2776)): #0 0x0000003a6b6d4f73 in poll () from /lib64/libc.so.6 #1 0x0000003757e3afbc in ?? () from /lib64/libglib-2.0.so.0 #2 0x0000003757e3b300 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x0000003758b680fe in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x0000003758b3df52 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x0000003758b3e324 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x0000003758a56fab in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x0000003758b21838 in ?? () from /usr/lib64/libQtCore.so.4 #8 0x0000003758a59d21 in ?? () from /usr/lib64/libQtCore.so.4 #9 0x0000003a6c20686a in start_thread () from /lib64/libpthread.so.0 #10 0x0000003a6b6de25d in clone () from /lib64/libc.so.6 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fe1285d3820 (LWP 2713)): [KCrash Handler] #5 0x0000003a6b6332f5 in raise () from /lib64/libc.so.6 #6 0x0000003a6b634b20 in abort () from /lib64/libc.so.6 #7 0x0000003758a52104 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/libQtCore.so.4 #8 0x0000003758a52256 in qFatal(char const*, ...) () from /usr/lib64/libQtCore.so.4 #9 0x00007fe119bdb222 in QString PackageKit::Util::enumToString<PackageKit::Client>(int, char const*, QString const&) () from /usr/lib64/libpackagekit-qt.so.11 #10 0x00007fe119bd0bc5 in PackageKit::Client::getTimeSinceAction(PackageKit::Client::Action) () from /usr/lib64/libpackagekit-qt.so.11 #11 0x00007fe119e0500b in ?? () from /usr/lib64/kde4/kded_kpackagekitd.so #12 0x00007fe119e0483c in QMetaObject::changeGuard(QObject**, QObject*) () from /usr/lib64/kde4/kded_kpackagekitd.so #13 0x0000003758b54cec in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #14 0x0000003758b4ebc3 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #15 0x0000003759d8ea8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #16 0x0000003759d95e3e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #17 0x000000375b804b86 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #18 0x0000003758b3f61c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #19 0x0000003758b6a622 in ?? () from /usr/lib64/libQtCore.so.4 #20 0x0000003758b6815d in ?? () from /usr/lib64/libQtCore.so.4 #21 0x0000003757e37afe in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #22 0x0000003757e3b1d8 in ?? () from /lib64/libglib-2.0.so.0 #23 0x0000003757e3b300 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #24 0x0000003758b680a6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #25 0x0000003759e2162e in ?? () from /usr/lib64/libQtGui.so.4 #26 0x0000003758b3df52 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #27 0x0000003758b3e324 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #28 0x0000003758b403c9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #29 0x000000375b20b37b in kdemain () from /usr/lib64/libkdeinit4_kded4.so #30 0x0000003a6b61ea2d in __libc_start_main () from /lib64/libc.so.6 #31 0x0000000000400709 in _start ()
$ kded4 --version Qt: 4.5.1 KDE: 4.2.3 (KDE 4.2.3) KDE Daemon: $Id: kded.cpp 944896 2009-03-26 13:00:10Z dfaure $ kdebase-workspace-4.2.3-5.fc11.x86_64
Do you experience this regularly? Thanks
please find which version of KPackageKit, packagekit-qt and Packagekit. Thanks.
yes, I do see this regularily, typically after a couple of minutes after login. I also saw kpackagekit crashing a day or two ago - this is what I've got: $ rpm -qa \*packagekit\* kpackagekit-0.4.0-7.fc11.x86_64
k, i need to know packageKit version too and packagekit-qt, as you updated a day or two, is about the same time PackageKit 0.4.8 seems to be released in fedora, and KPackageKit 0.4.0 does not work with PackageKit >= 0.4.7. This is problably the reason of this crashes, hopefully the new KPackageKit 0.4.1 will be available to you.
Ah, sorry, thought I didn't have any more packagekit bits in my system. Here we go: $ rpm -qa |grep -i packagekit kpackagekit-0.4.0-7.fc11.x86_64 PackageKit-yum-0.4.8-1.fc11.x86_64 PackageKit-yum-plugin-0.4.8-1.fc11.x86_64 PackageKit-qt-0.4.8-1.fc11.x86_64 PackageKit-gtk-module-0.4.8-1.fc11.x86_64 PackageKit-glib-0.4.8-1.fc11.x86_64 PackageKit-0.4.8-1.fc11.x86_64 So you're right: 0.4.8 vs 0.4.0 is probably the cause. Actually, all mirrors are down for me atm, probably due to the near release of Fedora 11. No problem, I'll wait four days and report back if the problem doesn't go away in the next update. Thanks.
Yes, that's the cause, we had to break API of packagekit-qt :( Sorry for the inconvenience, and thanks for the report, i believe as soon as 0.4.1 is available you'll be ok
I installed fedora 11 and tested the 0.4.1.1 package and it seems ok.
*** Bug 197220 has been marked as a duplicate of this bug. ***
*** Bug 197243 has been marked as a duplicate of this bug. ***
*** Bug 197373 has been marked as a duplicate of this bug. ***
*** Bug 225107 has been marked as a duplicate of this bug. ***
*** Bug 231335 has been marked as a duplicate of this bug. ***
*** Bug 238650 has been marked as a duplicate of this bug. ***
*** Bug 238582 has been marked as a duplicate of this bug. ***