Bug 227609

Summary:	App was just sitting there and crashed.
Product:	[Unmaintained] kpackagekit	Reporter:	Richie Ward <Richies>
Component:	general	Assignee:	Steven M. Parrish <smparrish>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, dantti12, ra.be.baerlin
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Richie Ward 2010-02-19 02:07:10 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.19.fc12.x86_64 x86_64

What I was doing when the application crashed:
Crashed for no apparant reason.

 -- Backtrace:
Application: KPackageKit (kpackagekitsmarticon), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fc2e55f9f89 in QMutex::lock() () from /usr/lib64/libQtCore.so.4
#6  0x00007fc2e56e3b72 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib64/libQtCore.so.4
#7  0x00007fc2e60ede41 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libpackagekit-qt.so.12
#8  0x00007fc2e60ef288 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12
#9  0x00007fc2e56f908c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00007fc2e5eb88cf in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#11 0x00007fc2e5eb8b64 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#12 0x00007fc2e56f908c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x00007fc2e5eb87ff in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#14 0x00007fc2e5eb8bcc in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#15 0x00007fc2e5e85e84 in ?? () from /usr/lib64/libQtDBus.so.4
#16 0x00007fc2e5e8d61f in ?? () from /usr/lib64/libQtDBus.so.4
#17 0x00007fc2e56f3401 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x00007fc2e3d4665c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007fc2e3d4d8ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00007fc2e6c3b8e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x00007fc2e56e3e6c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x00007fc2e56e4a42 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#23 0x00007fc2e570c573 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x00007fc2e011420e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x00007fc2e0117bf8 in ?? () from /lib64/libglib-2.0.so.0
#26 0x00007fc2e0117d1a in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x00007fc2e570c1e6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007fc2e3dd8ffe in ?? () from /usr/lib64/libQtGui.so.4
#29 0x00007fc2e56e2772 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x00007fc2e56e2b44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00007fc2e56e4cd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x000000000040a9eb in _start ()

Reported using DrKonqi

Comment 1 Dario Andres 2010-02-19 02:49:51 UTC

This is being tracked at bug 225494 Thanks

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

Comment 2 ra.be.baerlin 2010-02-20 15:03:26 UTC

This segmentation fault does appear on my system also.

But more over there are other strange things. First of all is that as usual the kpackagekitsmarticon is sitting in the systray. When it launches the messages of the updates are display over the buttons, which is not a major issue. Second, as of my memory, changes to the system are a privilege to "root", currently I am not asked for that password as no request-window appears. Another issue is that sometimes during downloading or installation a message is displayed that all is fine, has completed and an restart is required, which is definitely not correct as the procedure is still working. And last whilst running sometimes kpackagekit is started again and correctly complains that it can not gather exclusive access. 

Regards

Ralf Bertelsmann