Bug 227374 - software update completion notification
Summary: software update completion notification
Status: RESOLVED DUPLICATE of bug 225494
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
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-17 15:39 UTC by Michael N. Moran
Modified: 2010-02-17 16:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael N. Moran 2010-02-17 15:39: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

What I was doing when the application crashed:
After performing a system software update, I receive a crash notification. The update always seems to complete successfully.

 -- Backtrace:
Application: KPackageKit (kpackagekitsmarticon), signal: Segmentation fault
[KCrash Handler]
#5  0x0000003dbb054f89 in QMutex::lock() () from /usr/lib64/libQtCore.so.4
#6  0x0000003dbb13eb72 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib64/libQtCore.so.4
#7  0x0000003dbec1de41 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libpackagekit-qt.so.12
#8  0x0000003dbec1f288 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12
#9  0x0000003dbb15408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x0000003dba8558cf in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#11 0x0000003dba855b64 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#12 0x0000003dbb15408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x0000003dba8557ff in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#14 0x0000003dba855bcc in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#15 0x0000003dba822e84 in ?? () from /usr/lib64/libQtDBus.so.4
#16 0x0000003dba82a61f in ?? () from /usr/lib64/libQtDBus.so.4
#17 0x0000003dbb14e401 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x0000003dbc18f65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x0000003dbc1968ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x0000003dbd1f68e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x0000003dbb13ee6c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x0000003dbb13fa42 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#23 0x0000003dbb167573 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x0000003b7ac3920e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x0000003b7ac3cbf8 in ?? () from /lib64/libglib-2.0.so.0
#26 0x0000003b7ac3cd1a in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x0000003dbb1671e6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x0000003dbc221ffe in ?? () from /usr/lib64/libQtGui.so.4
#29 0x0000003dbb13d772 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x0000003dbb13db44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x0000003dbb13fcd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x000000000040a9eb in _start ()

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

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-17 16:11:26 UTC
This is being tracked at bug 225494. Thanks

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