Bug 249982 - kpackage crashes|bug report not allowing my to select dup report
Summary: kpackage crashes|bug report not allowing my to select dup report
Status: RESOLVED DUPLICATE of bug 225404
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-03 11:11 UTC by david a lawson
Modified: 2010-09-03 19:10 UTC (History)
1 user (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 david a lawson 2010-09-03 11:11:41 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.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
updating. the bug report also refused to allow me to view the duplicates listed in the dup reports box, suggesting a bug in itself. there are quite a few reports on kpackage crashing. many seemed related to my crash, but again after selecting the report that closely matched my crash, it would not allow that.

-- Backtrace:
Application: KPackageKit (kpackagekitsmarticon), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fcc40c02d3c in QMutex::lock (this=0x2507120) at thread/qmutex.cpp:151
#7  0x00007fcc40cfd3d2 in QCoreApplication::postEvent (receiver=0x25234f0, event=0x258c8a0, priority=0) at kernel/qcoreapplication.cpp:1141
#8  0x00007fcc4174e3a1 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libpackagekit-qt.so.12
#9  0x00007fcc4174fe88 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.12
#10 0x00007fcc40d127a7 in QMetaObject::activate (sender=0x24d5940, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x258c890) at kernel/qobject.cpp:3280
#11 0x00007fcc415183bf in QDBusConnectionInterface::serviceOwnerChanged (this=0x2507120, _t1=<value optimized out>, _t2=<value optimized out>, _t3=<value optimized out>)
    at .moc/release-shared/moc_qdbusconnectioninterface.cpp:210
#12 0x00007fcc41518664 in QDBusConnectionInterface::qt_metacall (this=0x24d5940, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5faaa240)
    at .moc/release-shared/moc_qdbusconnectioninterface.cpp:137
#13 0x00007fcc40d127a7 in QMetaObject::activate (sender=0x24d5940, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x258c890) at kernel/qobject.cpp:3280
#14 0x00007fcc415182ef in QDBusConnectionInterface::NameOwnerChanged (this=0x2507120, _t1=<value optimized out>, _t2=<value optimized out>, _t3=<value optimized out>)
    at .moc/release-shared/moc_qdbusconnectioninterface.cpp:238
#15 0x00007fcc415186cc in QDBusConnectionInterface::qt_metacall (this=0x24d5940, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5faaa600)
    at .moc/release-shared/moc_qdbusconnectioninterface.cpp:141
#16 0x00007fcc414da90e in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>)
    at qdbusintegrator.cpp:909
#17 0x00007fcc414e57ef in QDBusCallDeliveryEvent::placeMetaCall (this=0x2506c50, object=0x258c8a0) at qdbusintegrator_p.h:103
#18 0x00007fcc40d0c87e in QObject::event (this=0x24d5940, e=0x2507120) at kernel/qobject.cpp:1219
#19 0x00007fcc3fbcdcdc in QApplicationPrivate::notify_helper (this=0x23f76f0, receiver=0x24d5940, e=0x24f1250) at kernel/qapplication.cpp:4389
#20 0x00007fcc3fbd37cd in QApplication::notify (this=0x7fff5faab0f0, receiver=0x24d5940, e=0x24f1250) at kernel/qapplication.cpp:4270
#21 0x00007fcc42311eb6 in KApplication::notify (this=0x7fff5faab0f0, receiver=0x24d5940, event=0x24f1250) at ../../kdeui/kernel/kapplication.cpp:310
#22 0x00007fcc40cfaa8c in QCoreApplication::notifyInternal (this=0x7fff5faab0f0, receiver=0x24d5940, event=0x24f1250) at kernel/qcoreapplication.cpp:732
#23 0x00007fcc40cfd9b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x23d2490) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x23d2490) at kernel/qcoreapplication.cpp:1373
#25 0x00007fcc40d27043 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 0x00007fcc3b0ef8c2 in g_main_dispatch (context=0x23fc8c0) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:1960
#28 IA__g_main_context_dispatch (context=0x23fc8c0) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2513
#29 0x00007fcc3b0f3748 in g_main_context_iterate (context=0x23fc8c0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2591
#30 0x00007fcc3b0f38fc in IA__g_main_context_iteration (context=0x23fc8c0, may_block=1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2654
#31 0x00007fcc40d26b83 in QEventDispatcherGlib::processEvents (this=0x23d1be0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#32 0x00007fcc3fc7f80e in QGuiEventDispatcherGlib::processEvents (this=0x2507120, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007fcc40cf97b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#34 0x00007fcc40cf9b9c in QEventLoop::exec (this=0x7fff5faab040, flags=) at kernel/qeventloop.cpp:201
#35 0x00007fcc40cfdc4b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#36 0x000000000040b48b in _start ()

Possible duplicates by query: bug 249566, bug 249536, bug 249525, bug 249513, bug 249274.

Reported using DrKonqi
Comment 1 Daniel Nicoletti 2010-09-03 19:10:34 UTC

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