Application that crashed: kded4 Version of the application: $Id: kded.cpp 1031638 2009-10-05 16:59:11Z lunakl $ KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.31.9-174.fc12.i686 i686 What I was doing when the application crashed: after sleep mode mulitasking w/kwrite & firefox ; nothing else active except some stuff I wasn't paying attention to: dolphin FSM & package tool -- Backtrace: Application: KDE Daemon (kded4), signal: Segmentation fault [KCrash Handler] #6 0x0375f90a in QMutex::lock() () from /usr/lib/libQtCore.so.4 #7 0x038559d5 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/libQtCore.so.4 #8 0x03855cdd in QCoreApplication::postEvent(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #9 0x03865405 in QObject::deleteLater() () from /usr/lib/libQtCore.so.4 #10 0x00e8966f in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libpackagekit-qt.so.12 #11 0x00e8ac63 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.12 #12 0x0386bc0c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #13 0x0386c843 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #14 0x007be350 in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4 #15 0x007be6ab in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4 #16 0x0386bc0c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #17 0x0386c843 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #18 0x007be1f0 in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4 #19 0x007be73b in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4 #20 0x00787a3c in ?? () from /usr/lib/libQtDBus.so.4 #21 0x0078f9a8 in ?? () from /usr/lib/libQtDBus.so.4 #22 0x03865f96 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #23 0x0503bb24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #24 0x05043281 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #25 0x0482307b in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #26 0x03855d73 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #27 0x03856972 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #28 0x03856b2e in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #29 0x03880f40 in ?? () from /usr/lib/libQtCore.so.4 #30 0x00aa7128 in g_main_dispatch (context=<value optimized out>) at gmain.c:1960 #31 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513 #32 0x00aaaa58 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591 #33 0x00aaab84 in IA__g_main_context_iteration (context=0x8d60490, may_block=<value optimized out>) at gmain.c:2654 #34 0x03880b6d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #35 0x050db356 in ?? () from /usr/lib/libQtGui.so.4 #36 0x038542aa in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #37 0x0385470a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #38 0x03856bf7 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #39 0x0503b9a8 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #40 0x00387815 in kdemain () from /usr/lib/libkdeinit4_kded4.so #41 0x0804868c in _start () Reported using DrKonqi
Fixed recently. Please read bug 219590 comment 104. Regards *** This bug has been marked as a duplicate of bug 219590 ***