Bug 228338 - kpackagekit crashes after completing update
Summary: kpackagekit crashes after completing update
Status: RESOLVED DUPLICATE of bug 225404
Alias: None
Product: kpackagekit
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-24 17:53 UTC by Nestal Wan
Modified: 2010-02-24 22:28 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nestal Wan 2010-02-24 17:53:19 UTC
Application that crashed: kpackagekit
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 crashes everytime after doing it job. reproducible.

 -- Backtrace:
Application: KPackageKit (kpackagekit), signal: Segmentation fault
[KCrash Handler]
#5  0x00000032e5854f89 in QMutex::lock() () from /usr/lib64/libQtCore.so.4
#6  0x00000032e593eb72 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib64/libQtCore.so.4
#7  0x00000032ea21de41 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libpackagekit-qt.so.12
#8  0x00000032ea21f288 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12
#9  0x00000032e595408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00000032e6a558cf in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#11 0x00000032e6a55b64 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#12 0x00000032e595408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x00000032e6a557ff in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#14 0x00000032e6a55bcc in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#15 0x00000032e6a22e84 in ?? () from /usr/lib64/libQtDBus.so.4
#16 0x00000032e6a2a61f in ?? () from /usr/lib64/libQtDBus.so.4
#17 0x00000032e594e401 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x000000332f58f65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x000000332f5968ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00000033305f68e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x00000032e593ee6c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x00000032e593fa42 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#23 0x00000032e5967573 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x00000032dd03920e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x00000032dd03cbf8 in ?? () from /lib64/libglib-2.0.so.0
#26 0x00000032dd03cd1a in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x00000032e59671e6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x000000332f621ffe in ?? () from /usr/lib64/libQtGui.so.4
#29 0x00000032e593d772 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x00000032e593db44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00000032e593fcd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x0000000000406082 in _start ()

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

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-24 22:28:20 UTC
This is being tracked at bug 225404. Thanks

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