Bug 250816 - Kpackagekit crashed after being open for several minutes without doing anything
Summary: Kpackagekit crashed after being open for several minutes without doing anything
Status: RESOLVED DUPLICATE of bug 225494
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
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-09-10 20:17 UTC by Lindsay Smart
Modified: 2010-09-10 22:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (6.60 KB, text/plain)
2010-09-10 22:18 UTC, Sebastian Morkisch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lindsay Smart 2010-09-10 20:17:44 UTC
Application: kpackagekit (0.5.4)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
Kpackagekit crashed, I hadn't done anything with it for a few minutes.

 -- Backtrace:
Application: KPackageKit (kpackagekit), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f26da7350a3 in QObjectPrivate::isSignalConnected (sender=0xcd0300, m=<value optimized out>, local_signal_index=11, argv=0x7fff4885c720) at kernel/qobject_p.h:227
#6  QMetaObject::activate (sender=0xcd0300, m=<value optimized out>, local_signal_index=11, argv=0x7fff4885c720) at kernel/qobject.cpp:3218
#7  0x00007f26db159d2f in PackageKit::Transaction::finished(PackageKit::Transaction::ExitStatus, unsigned int) () from /usr/lib/libpackagekit-qt.so.12
#8  0x00007f26db155399 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libpackagekit-qt.so.12
#9  0x00007f26db156e88 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.12
#10 0x00007f26da734e3f in QMetaObject::activate (sender=0xdc8ca0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293
#11 0x00007f26daf2009f in QDBusConnectionInterface::serviceOwnerChanged (this=0xd, _t1=<value optimized out>, _t2=<value optimized out>, _t3=<value optimized out>)
    at .moc/release-shared/moc_qdbusconnectioninterface.cpp:210
#12 0x00007f26daf20344 in QDBusConnectionInterface::qt_metacall (this=0xdc8ca0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4885cb70)
    at .moc/release-shared/moc_qdbusconnectioninterface.cpp:137
#13 0x00007f26da734e3f in QMetaObject::activate (sender=0xdc8ca0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293
#14 0x00007f26daf1ffcf in QDBusConnectionInterface::NameOwnerChanged (this=0xd, _t1=<value optimized out>, _t2=<value optimized out>, _t3=<value optimized out>)
    at .moc/release-shared/moc_qdbusconnectioninterface.cpp:238
#15 0x00007f26daf203ac in QDBusConnectionInterface::qt_metacall (this=0xdc8ca0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4885cf30)
    at .moc/release-shared/moc_qdbusconnectioninterface.cpp:141
#16 0x00007f26daee4486 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>)
    at qdbusintegrator.cpp:904
#17 0x00007f26daeef05f in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib/libQtDBus.so.4
#18 0x00007f26da731d49 in QObject::event (this=0xdc8ca0, e=0xd86ac0) at kernel/qobject.cpp:1248
#19 0x00007f26d963e22c in QApplicationPrivate::notify_helper (this=0xc3efc0, receiver=0xdc8ca0, e=0xd86ac0) at kernel/qapplication.cpp:4300
#20 0x00007f26d96446fb in QApplication::notify (this=0x7fff4885da20, receiver=0xdc8ca0, e=0xd86ac0) at kernel/qapplication.cpp:4183
#21 0x00007f26db810526 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#22 0x00007f26da72206c in QCoreApplication::notifyInternal (this=0x7fff4885da20, receiver=0xdc8ca0, event=0xd86ac0) at kernel/qcoreapplication.cpp:704
#23 0x00007f26da7247e7 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0xc1a4c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xc1a4c0) at kernel/qcoreapplication.cpp:1345
#25 0x00007f26da74b9d3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#26 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#27 0x00007f26d58358c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#28 0x00007f26d5839748 in ?? () from /lib/libglib-2.0.so.0
#29 0x00007f26d58398fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#30 0x00007f26da74b513 in QEventDispatcherGlib::processEvents (this=0xc19c10, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#31 0x00007f26d96ee46e in QGuiEventDispatcherGlib::processEvents (this=0xd, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007f26da720992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#33 0x00007f26da720d6c in QEventLoop::exec (this=0x7fff4885d970, flags=) at kernel/qeventloop.cpp:201
#34 0x00007f26da724aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#35 0x00000000004067c2 in _start ()

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

Possible duplicates by query: bug 249984, bug 249926, bug 249203, bug 248312, bug 247291.

Reported using DrKonqi
Comment 1 Daniel Nicoletti 2010-09-10 22:15:49 UTC

*** This bug has been marked as a duplicate of bug 225494 ***
Comment 2 Sebastian Morkisch 2010-09-10 22:18:04 UTC
Created attachment 51533 [details]
New crash information added by DrKonqi

I clicked and read a couple of leaf elements from the possible updates contained in the update tree of 6 elements. The system has very few crash moments, so I suppose it is quite stable. I did not install any software before, which might have caused a destabilizing momentum. The last action I fired was closing the info window which popped up from the taskbar informing me that there are no messages from the system. The only software apart from the deamons and other X related stuff I ran is KTorrent.

Hope this helps a bit to trace the error...