Bug 226384

Summary: kpackagekit is crashing during update
Product: [Unmaintained] kpackagekit Reporter: kevin C <linux>
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 kevin C 2010-02-11 21:12:26 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.3.fc12.x86_64 x86_64
Distribution: "Fedora release 12 (Constantine)"

What I was doing when the application crashed:
I just want to update my system, the backend is yum. The program crash during the update process.

 -- Backtrace:
Application: KPackageKit (kpackagekitsmarticon), signal: Segmentation fault
[KCrash Handler]
#5  0x0000003382f54d54 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#6  0x0000003385421faf in PackageKit::Transaction::finished(PackageKit::Transaction::ExitStatus, unsigned int) () from /usr/lib64/libpackagekit-qt.so.12
#7  0x000000338541de39 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libpackagekit-qt.so.12
#8  0x000000338541f288 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12
#9  0x0000003382f5408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00000033826558cf in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#11 0x0000003382655b64 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#12 0x0000003382f5408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x00000033826557ff in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#14 0x0000003382655bcc in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#15 0x0000003382622e84 in ?? () from /usr/lib64/libQtDBus.so.4
#16 0x000000338262a61f in ?? () from /usr/lib64/libQtDBus.so.4
#17 0x0000003382f4e401 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x000000338598f65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00000033859968ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00000033841f68e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x0000003382f3ee6c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x0000003382f3fa42 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#23 0x0000003382f67573 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x000000338123920e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x000000338123cbf8 in ?? () from /lib64/libglib-2.0.so.0
#26 0x000000338123cd1a in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x0000003382f671e6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x0000003385a21ffe in ?? () from /usr/lib64/libQtGui.so.4
#29 0x0000003382f3d772 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x0000003382f3db44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x0000003382f3fcd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x000000000040a9eb in _start ()

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

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-11 23:44:53 UTC
Merging with bug 225494. Thanks

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