228193 2010-02-23 13:04:34 +0000 PackageKit sudden crash without user operation 2010-02-23 17:40:19 +0000 1 1 10 Unmaintained kpackagekit general unspecified Unlisted Binaries Linux RESOLVED DUPLICATE 225494 NOR crash --- 0 marcin.rzeznicki smparrish andresbajotierra dantti12 0 oldest_to_newest 922974 0 marcin.rzeznicki 2010-02-23 13:04:34 +0000 Application that crashed: kpackagekitsmarticon Version of the application: 0.5.4 KDE Version: 4.3.5 (KDE 4.3.5) Qt Version: 4.5.3 Operating System: Linux 2.6.31.12-174.2.22.fc12.i686.PAE i686 What I was doing when the application crashed: KPackageKit crashed this time without my even interfering with it. I was reviewing update, switched to my browser to see something and then it crashed -- Backtrace: Application: KPackageKit (kpackagekitsmarticon), signal: Segmentation fault [KCrash Handler] #6 0x07c6d861 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #7 0x07f1790a in PackageKit::Transaction::finished(PackageKit::Transaction::ExitStatus, unsigned int) () from /usr/lib/libpackagekit-qt.so.12 #8 0x07f12b17 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libpackagekit-qt.so.12 #9 0x07f14113 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.12 #10 0x07c6cc0c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #11 0x07c6d843 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #12 0x07ecb350 in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4 #13 0x07ecb6ab in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4 #14 0x07c6cc0c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #15 0x07c6d843 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #16 0x07ecb1f0 in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4 #17 0x07ecb73b in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4 #18 0x07e94a3c in ?? () from /usr/lib/libQtDBus.so.4 #19 0x07e9c9a8 in ?? () from /usr/lib/libQtDBus.so.4 #20 0x07c66f96 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #21 0x05e84b24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #22 0x05e8c281 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #23 0x068f48cb in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #24 0x07c56d73 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #25 0x07c57972 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #26 0x07c57b2e in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #27 0x07c81f40 in ?? () from /usr/lib/libQtCore.so.4 #28 0x0016af88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #29 0x0016e8b8 in ?? () from /lib/libglib-2.0.so.0 #30 0x0016e9e4 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #31 0x07c81b6d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #32 0x05f24356 in ?? () from /usr/lib/libQtGui.so.4 #33 0x07c552aa in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #34 0x07c5570a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #35 0x07c57bf7 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #36 0x05e849a8 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #37 0x080506a9 in _start () This bug may be a duplicate of or related to bug 227226 Reported using DrKonqi 923063 1 andresbajotierra 2010-02-23 17:40:19 +0000 Merging with bug 225494. Thanks *** This bug has been marked as a duplicate of bug 225494 ***