Application: kpackagekitsmarticon (0.5.4) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.2 Operating System: Linux 2.6.32-28-generic-pae i686 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: The programm crashed while i was trying to upgrade my system to the new version. A message box just appeared about an error during the upgrade ("Could not calculate the upgrade... E:Error, pkgProblemResolver::Resolve ...") Otherwise nothing unusual -- Backtrace: Application: KPackageKit (kpackagekitsmarticon), signal: Segmentation fault [KCrash Handler] #6 0xb6d9ef37 in QMutex::lock() () from /usr/lib/libQtCore.so.4 #7 0xb6ea6634 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/libQtCore.so.4 #8 0xb6ea69ac in QCoreApplication::postEvent(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #9 0xb6eb68a4 in QObject::deleteLater() () from /usr/lib/libQtCore.so.4 #10 0xb70d4384 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libpackagekit-qt.so.12 #11 0xb70d6453 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.12 #12 0xb6eabc9a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #13 0xb6eba3d5 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #14 0xb70a0d9f in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4 #15 0xb70a10c3 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4 #16 0xb6eabc9a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #17 0xb6eba3d5 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #18 0xb70a0c4f in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4 #19 0xb70a1153 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4 #20 0xb7061b34 in ?? () from /usr/lib/libQtDBus.so.4 #21 0xb706cea7 in ?? () from /usr/lib/libQtDBus.so.4 #22 0xb6eb73fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #23 0xb60db4dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #24 0xb60e205e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #25 0xb75de40a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #26 0xb6ea6a3b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #27 0xb6ea9473 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #28 0xb6ea95dd in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #29 0xb6ed2adf in ?? () from /usr/lib/libQtCore.so.4 #30 0xb585f5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #31 0xb58632d8 in ?? () from /lib/libglib-2.0.so.0 #32 0xb58634b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #33 0xb6ed25d5 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #34 0xb619b135 in ?? () from /usr/lib/libQtGui.so.4 #35 0xb6ea5059 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #36 0xb6ea54aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #37 0xb6ea969f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #38 0xb60db577 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #39 0x080510c1 in _start () This bug may be a duplicate of or related to bug 263549, bug 260247. Possible duplicates by query: bug 263549, bug 263470, bug 262587, bug 260355, bug 260247. Reported using DrKonqi
[Comment from a bug triager] This issue is fixed since KPackageKit 0.6.0. The bug was being tracked at bug 225494. Merging. Thanks *** This bug has been marked as a duplicate of bug 225494 ***