Bug 248683 - KPackageKit crash during Chromium updates and during Chromium was running
Summary: KPackageKit crash during Chromium updates and during Chromium was running
Status: RESOLVED DUPLICATE of bug 225494
Alias: None
Product: kpackagekit
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-22 11:22 UTC by gianted
Modified: 2010-08-22 17:14 UTC (History)
1 user (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 gianted 2010-08-22 11:22:21 UTC
Application: kpackagekitsmarticon (0.5.4)
KDE Platform Version: 4.5.00 (KDE 4.5.0)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-020635rc6-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

# I selected today's chromium proposed updates; then KPackageKit started to download and probably when finished, it crashed during updates application.

# Chromium was running during updates. Anyway, these were probably applied because when I restarted both Chromium and the bug report assistant, this last one detected all previous proposed updates except for chromium.

- Custom settings of the system:

# I'm using KDE4.5 from
http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu

# Chromium 5.0.375.125 (53311) Ubuntu 10.04
Running during updates.

-- Backtrace:
Application: KPackageKit (kpackagekitsmarticon), signal: Segmentation fault
[KCrash Handler]
#7  0xb6d804d9 in QMutex::lock (this=0x82d69f0) at thread/qmutex.cpp:151
#8  0xb6e89564 in QCoreApplication::postEvent (receiver=0x8374078, event=0x837df08, priority=0) at kernel/qcoreapplication.cpp:1141
#9  0xb6e898ec in QCoreApplication::postEvent (receiver=0x8374078, event=0x837df08) at kernel/qcoreapplication.cpp:1094
#10 0xb6e98084 in QObject::deleteLater (this=0x8374078) at kernel/qobject.cpp:2131
#11 0xb70d5384 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libpackagekit-qt.so.12
#12 0xb70d7453 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.12
#13 0xb6e8c6ca in QMetaObject::metacall (object=0x83165c0, cl=137838712, idx=6, argv=0xbfdb4d40) at kernel/qmetaobject.cpp:237
#14 0xb6e9f455 in QMetaObject::activate (sender=0x8315c58, m=0xb70b9c88, local_signal_index=2, argv=0xbfdb4d40) at kernel/qobject.cpp:3280
#15 0xb70a195f in QDBusConnectionInterface::serviceOwnerChanged (this=0x8315c58, _t1=..., _t2=..., _t3=...) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:210
#16 0xb70a1c83 in QDBusConnectionInterface::qt_metacall (this=0x8315c58, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfdb4f10) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:137
#17 0xb6e8c6ca in QMetaObject::metacall (object=0x8315c58, cl=137838712, idx=7, argv=0xbfdb4f10) at kernel/qmetaobject.cpp:237
#18 0xb6e9f455 in QMetaObject::activate (sender=0x8315c58, m=0xb70b9c88, local_signal_index=6, argv=0xbfdb4f10) at kernel/qobject.cpp:3280
#19 0xb70a180f in QDBusConnectionInterface::NameOwnerChanged (this=0x8315c58, _t1=..., _t2=..., _t3=...) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:238
#20 0xb70a1d13 in QDBusConnectionInterface::qt_metacall (this=0x8315c58, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfdb511c) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:141
#21 0xb70601b4 in QDBusConnectionPrivate::deliverCall (this=0x83145e0, object=0x8315c58, msg=..., metaTypes=..., slotIdx=11) at qdbusintegrator.cpp:909
#22 0xb706b8f7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8378430, object=0x8315c58) at qdbusintegrator_p.h:103
#23 0xb6e99462 in QObject::event (this=0x8315c58, e=0x730075) at kernel/qobject.cpp:1219
#24 0xb62f30cc in QApplicationPrivate::notify_helper (this=0x824e1c0, receiver=0x8315c58, e=0x8378430) at kernel/qapplication.cpp:4389
#25 0xb62f911e in QApplication::notify (this=0xbfdb59e8, receiver=0x8315c58, e=0x8378430) at kernel/qapplication.cpp:3791
#26 0xb75f282a in KApplication::notify (this=0xbfdb59e8, receiver=0x8315c58, event=0x8378430) at ../../kdeui/kernel/kapplication.cpp:310
#27 0xb6e8696b in QCoreApplication::notifyInternal (this=0xbfdb59e8, receiver=0x8315c58, event=0x8378430) at kernel/qcoreapplication.cpp:732
#28 0xb6e89bcb in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x82310d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x82310d0) at kernel/qcoreapplication.cpp:1373
#30 0xb6e89d8d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#31 0xb6eb569f in QCoreApplication::sendPostedEvents (s=0x8250b10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#32 postEventSourceDispatch (s=0x8250b10) at kernel/qeventdispatcher_glib.cpp:276
#33 0xb55c75e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#34 0xb55cb2d8 in ?? () from /lib/libglib-2.0.so.0
#35 0xb55cb4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#36 0xb6eb5195 in QEventDispatcherGlib::processEvents (this=0x8230bf8, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#37 0xb63b43b5 in QGuiEventDispatcherGlib::processEvents (this=0x8230bf8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#38 0xb6e85419 in QEventLoop::processEvents (this=0xbfdb5944, flags=) at kernel/qeventloop.cpp:149
#39 0xb6e8589a in QEventLoop::exec (this=0xbfdb5944, flags=...) at kernel/qeventloop.cpp:201
#40 0xb6e89e4f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#41 0xb62f1ef7 in QApplication::exec () at kernel/qapplication.cpp:3665
#42 0x08051111 in _start ()

This bug may be a duplicate of or related to bug 225404.

Possible duplicates by query: bug 247948, bug 247352, bug 247307, bug 247155, bug 247088.

Reported using DrKonqi
Comment 1 Daniel Nicoletti 2010-08-22 17:14:52 UTC

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