Bug 194544

Summary: crash while downlowding jaunty iso-file
Product: [Applications] kget Reporter: m.wege
Component: generalAssignee: KGet authors <kget>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, mieszkoslusarczyk
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description m.wege 2009-05-29 14:50:28 UTC
Application that crashed: kget
Version of the application: 2.2.85
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-020630rc6-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
The crash occuring shortly before the download of the jaunty iso.

 -- Backtrace:
Application: KGet (kget), signal: Segmentation fault
[KCrash Handler]
#6  0x0b000020 in ?? ()
#7  0xb40da480 in Segment::createTransfer (this=0xa4bfb60, src=@0xbfd1caac) at /usr/include/qt4/QtCore/qobject.h:308
#8  0xb40da4ae in Segment::restartTransfer (this=0xa4bfb60, url=@0xbfd1caac) at /build/buildd/kdenetwork-4.2.85/kget/transfer-plugins/multisegmentkio/segmentfactory.cpp:102
#9  0xb40da5db in SegmentFactory::slotSegmentTimeOut (this=0xa418e60) at /build/buildd/kdenetwork-4.2.85/kget/transfer-plugins/multisegmentkio/segmentfactory.cpp:406
#10 0xb40dcabb in SegmentFactory::qt_metacall (this=0xa418e60, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfd1cb68)
    at /build/buildd/kdenetwork-4.2.85/obj-i486-linux-gnu/kget/transfer-plugins/multisegmentkio/segmentfactory.moc:167
#11 0xb6a26a58 in QMetaObject::activate (sender=0xa3ee8d0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3120
#12 0xb6a276e2 in QMetaObject::activate (sender=0xa3ee8d0, m=0xb6b02908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3194
#13 0xb6a2be57 in QSingleShotTimer::timeout (this=0xa3ee8d0) at .moc/release-shared/qtimer.moc:76
#14 0xb6a2bf7c in QSingleShotTimer::timerEvent (this=0xa3ee8d0) at kernel/qtimer.cpp:298
#15 0xb6a20f0f in QObject::event (this=0xa3ee8d0, e=0xbfd1cfec) at kernel/qobject.cpp:1082
#16 0xb6ec7bcc in QApplicationPrivate::notify_helper (this=0x9fecc70, receiver=0xa3ee8d0, e=0xbfd1cfec) at kernel/qapplication.cpp:4057
#17 0xb6ecfede in QApplication::notify (this=0xbfd1d278, receiver=0xa3ee8d0, e=0xbfd1cfec) at kernel/qapplication.cpp:3604
#18 0xb7e1bc9d in KApplication::notify (this=0xbfd1d278, receiver=0xa3ee8d0, event=0xbfd1cfec) at /build/buildd/kde4libs-4.2.85/kdeui/kernel/kapplication.cpp:307
#19 0xb6a107ab in QCoreApplication::notifyInternal (this=0xbfd1d278, receiver=0xa3ee8d0, event=0xbfd1cfec) at kernel/qcoreapplication.cpp:610
#20 0xb6a3fb31 in QTimerInfoList::activateTimers (this=0x9fef3bc) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 0xb6a3c280 in timerSourceDispatch (source=0x9fef388) at kernel/qeventdispatcher_glib.cpp:164
#22 0xb6026b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb602a0eb in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb602a268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb6a3c1d8 in QEventDispatcherGlib::processEvents (this=0x9fe2e38, flags={i = -1076768408}) at kernel/qeventdispatcher_glib.cpp:324
#26 0xb6f69765 in QGuiEventDispatcherGlib::processEvents (this=0x9fe2e38, flags={i = -1076768360}) at kernel/qguieventdispatcher_glib.cpp:202
#27 0xb6a0edda in QEventLoop::processEvents (this=0xbfd1d210, flags={i = -1076768296}) at kernel/qeventloop.cpp:149
#28 0xb6a0f21a in QEventLoop::exec (this=0xbfd1d210, flags={i = -1076768232}) at kernel/qeventloop.cpp:200
#29 0xb6a116c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#30 0xb6ec7a47 in QApplication::exec () at kernel/qapplication.cpp:3526
#31 0x0809f93a in main (argc=2, argv=0xbfd1d464) at /build/buildd/kdenetwork-4.2.85/kget/main.cpp:153
Comment 1 Dario Andres 2009-05-29 15:39:57 UTC
I wonder if this could be related in some way to bug 194427.
Comment 2 m.wege 2009-05-29 15:47:00 UTC
I can not tell, of course its the same app. I can not read those backtraces very good. But may be it has something to do with downloading from multiple sources.
Comment 3 Urs Wolfer 2009-06-07 19:09:51 UTC

*** This bug has been marked as a duplicate of bug 194427 ***
Comment 4 Dario Andres 2009-06-19 17:48:22 UTC
*** Bug 197157 has been marked as a duplicate of this bug. ***