Bug 228277

Summary: KPackageKit crashed after transaction is finished
Product: [Unmaintained] kpackagekit Reporter: Vincent Tassy <timetre>
Component: generalAssignee: Steven M. Parrish <smparrish>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, dantti12
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Vincent Tassy 2010-02-24 09:56:11 UTC
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.x86_64 x86_64
Distribution: "Fedora release 12 (Constantine)"

What I was doing when the application crashed:
KPackageKit often crashes when finished updating the system

 -- Backtrace:
Application: KPackageKit (kpackagekitsmarticon), signal: Segmentation fault
[KCrash Handler]
#5  0x000000388cb53eed in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#6  0x0000003890a21faf in PackageKit::Transaction::finished(PackageKit::Transaction::ExitStatus, unsigned int) () from /usr/lib64/libpackagekit-qt.so.12
#7  0x0000003890a1de39 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libpackagekit-qt.so.12
#8  0x0000003890a1f288 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12
#9  0x000000388cb5408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x000000388d8558cf in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#11 0x000000388d855b64 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#12 0x000000388cb5408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x000000388d8557ff in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#14 0x000000388d855bcc in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#15 0x000000388d822e84 in ?? () from /usr/lib64/libQtDBus.so.4
#16 0x000000388d82a61f in ?? () from /usr/lib64/libQtDBus.so.4
#17 0x000000388cb4e401 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x0000003798b8f65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x0000003798b968ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00000037979f68e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x000000388cb3ee6c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x000000388cb3fa42 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#23 0x000000388cb67573 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x0000003a5ca3920e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x0000003a5ca3cbf8 in ?? () from /lib64/libglib-2.0.so.0
#26 0x0000003a5ca3cd1a in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x000000388cb671e6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x0000003798c21ffe in ?? () from /usr/lib64/libQtGui.so.4
#29 0x000000388cb3d772 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x000000388cb3db44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x000000388cb3fcd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x000000000040a9eb in _start ()

This bug may be a duplicate of or related to bug 227294

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-24 13:38:40 UTC
This is being tracked at bug 225494. Regards

*** This bug has been marked as a duplicate of bug 225494 ***