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.6-166.fc12.i686.PAE i686 What I was doing when the application crashed: Every time a message is moved, be it by hand, by filter, or by Expire, KMail crashes. I have also seen the message, a couple of times: Could not upload the message dated from <unknown> with subject <unknown> to the server. The destination folder was: Borgx/Trash The server reported: Append aborted I've no idea whether this is related or not. -- Backtrace: Application: KDE Daemon (kded4), signal: Segmentation fault [KCrash Handler] #6 0x05614861 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #7 0x0599f4fa in PackageKit::Transaction::finished(PackageKit::Transaction::ExitStatus, unsigned int) () from /usr/lib/libpackagekit-qt.so.12 #8 0x0599a667 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libpackagekit-qt.so.12 #9 0x0599bc63 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.12 #10 0x05613c0c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #11 0x05614843 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #12 0x007d7350 in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4 #13 0x007d76ab in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4 #14 0x05613c0c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #15 0x05614843 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #16 0x007d71f0 in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4 #17 0x007d773b in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4 #18 0x007a0a3c in ?? () from /usr/lib/libQtDBus.so.4 #19 0x007a89a8 in ?? () from /usr/lib/libQtDBus.so.4 #20 0x0560df96 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #21 0x05e97b24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #22 0x05e9f281 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #23 0x0698e07b in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #24 0x055fdd73 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #25 0x055fe972 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #26 0x055feb2e in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #27 0x05628f40 in ?? () from /usr/lib/libQtCore.so.4 #28 0x00c75128 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #29 0x00c78a58 in ?? () from /lib/libglib-2.0.so.0 #30 0x00c78b84 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #31 0x05628b6d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #32 0x05f37356 in ?? () from /usr/lib/libQtGui.so.4 #33 0x055fc2aa in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #34 0x055fc70a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #35 0x055febf7 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #36 0x05e979a8 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #37 0x007fd815 in kdemain () from /usr/lib/libkdeinit4_kded4.so #38 0x0804868c in _start () Reported using DrKonqi
Additional package info: rpm -q qt kdelibs kdepim qt-4.5.3-9.fc12.i686 kdelibs-4.3.4-1.fc12.i686 kdepim-4.3.4-1.fc12.i686
This crash is related to the package manager. Merging with bug 219590. Thanks *** This bug has been marked as a duplicate of bug 219590 ***