Bug 221147

Summary: Normally working in KDE
Product: [Unmaintained] kpackagekit Reporter: Marian Zsemlye <koapa>
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 Marian Zsemlye 2010-01-03 20:20:40 UTC
Application that crashed: kded4
Version of the application: $Id: kded.cpp 1031638 2009-10-05 16:59:11Z lunakl $
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.9-174.fc12.x86_64 x86_64

What I was doing when the application crashed:
This error occures once a linux run. It's happenning in every app, the is nothing, that should cause this bug.

 -- Backtrace:
Application: KDE démon (kded4), signal: Segmentation fault
[KCrash Handler]
#5  0x0000003948e54f89 in QMutex::lock() () from /usr/lib64/libQtCore.so.4
#6  0x0000003948f3eb72 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib64/libQtCore.so.4
#7  0x000000394ba1e091 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libpackagekit-qt.so.12
#8  0x000000394ba1f948 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12
#9  0x0000003948f5408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x000000394a8558cf in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#11 0x000000394a855b64 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#12 0x0000003948f5408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x000000394a8557ff in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
#14 0x000000394a855bcc in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtDBus.so.4
#15 0x000000394a822e84 in ?? () from /usr/lib64/libQtDBus.so.4
#16 0x000000394a82a61f in ?? () from /usr/lib64/libQtDBus.so.4
#17 0x0000003948f4e401 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x000000394bf8f65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x000000394bf968ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x000000394d411a66 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x0000003948f3ee6c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x0000003948f3fa42 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#23 0x0000003948f67573 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x000000394023922e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x000000394023cc18 in ?? () from /lib64/libglib-2.0.so.0
#26 0x000000394023cd3a in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x0000003948f671e6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x000000394c021ffe in ?? () from /usr/lib64/libQtGui.so.4
#29 0x0000003948f3d772 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x0000003948f3db44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x0000003948f3fcd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x0000003947e0b6eb in kdemain () from /usr/lib64/libkdeinit4_kded4.so
#33 0x000000393da1eb1d in __libc_start_main () from /lib64/libc.so.6
#34 0x0000000000400709 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-03 20:25:42 UTC
This is a package management issue: bug 219590. Thanks

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