Bug 156531

Today I downloaded a file to an external USB device via kget. As the download stalled I paused the download. After that, kget crashed with the same backtrace as above. So maybe it crashed the first time not because the disk was full, but because it paused (due to the disk being full)?
However, I regrettably still cannot reproduce this bug.

Backtrace:
Application: KGet (kget), signal SIGSEGV
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb64976d0 (LWP 5825)]
[KCrash handler]
#6  KJob::kill (this=0x0, verbosity=KJob::EmitResult)
    at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdecore/jobs/kjob.cpp:106
#7  0xb4f308d7 in Segment::stopTransfer (this=0x81cec18)
    at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kget/transfer-plugins/multisegmentkio/segmentfactory.cpp:78
#8  0xb4f30a9d in ~SegmentFactory (this=0x81a8d50)
    at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kget/transfer-plugins/multisegmentkio/segmentfactory.cpp:184
#9  0xb73a3fd7 in QObject::event (this=0x81a8d50, e=0x809f3d8)
    at kernel/qobject.cpp:1105
#10 0xb6a34e8a in QApplicationPrivate::notify_helper (this=0x80a4b80, 
    receiver=0x81a8d50, e=0x93b92d8) at kernel/qapplication.cpp:3556
#11 0xb6a3677a in QApplication::notify (this=0xbfe695f0, receiver=0x81a8d50, 
    e=0x93b92d8) at kernel/qapplication.cpp:3115
#12 0xb7dbd083 in KApplication::notify (this=0xbfe695f0, receiver=0x81a8d50, 
    event=0x93b92d8)
    at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdeui/kernel/kapplication.cpp:314
#13 0xb7392d7b in QCoreApplication::notifyInternal (this=0xbfe695f0, 
    receiver=0x81a8d50, event=0x93b92d8) at kernel/qcoreapplication.cpp:530
#14 0xb739421a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, 
    event_type=0, data=0x8093f58) at kernel/qcoreapplication.h:200
#15 0xb73bc905 in QEventDispatcherUNIX::processEvents (this=0x809eb28, 
    flags=@0xbfe694e8) at kernel/qeventdispatcher_unix.cpp:858
#16 0xb6abecce in QEventDispatcherX11::processEvents (this=0x809eb28, 
    flags=@0xbfe69514) at kernel/qeventdispatcher_x11.cpp:145
#17 0xb7392191 in QEventLoop::processEvents (this=0xbfe69580, 
    flags=@0xbfe69548) at kernel/qeventloop.cpp:140
#18 0xb739229a in QEventLoop::exec (this=0xbfe69580, flags=@0xbfe69588)
    at kernel/qeventloop.cpp:186
#19 0xb7394626 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:759
#20 0xb6a34487 in QApplication::exec () at kernel/qapplication.cpp:3053
#21 0x08086f03 in main (argc=2, argv=0xbfe69794)
    at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kget/main.cpp:150
#22 0xb66e5fdc in __libc_start_main (main=0x8086660 <main>, argc=2, 
    ubp_av=0xbfe69794, init=0x8087820 <__libc_csu_init>, 
    fini=0x8087810 <__libc_csu_fini>, rtld_fini=0xb7f28100 <_dl_fini>, 
    stack_end=0xbfe6978c) at libc-start.c:229
#23 0x0805e351 in _start ()
#0  0xffffe410 in __kernel_vsyscall ()

If the fault is that there is not enough disk space, fixing this should fix even an old wish: bug #57373.

Can someone try if it works now, it shouldn't crash at all...

Lukas

Oliver: can you reproduce the crash with a recent KDE ? Thanks

Hi!
No, I actually can no longer reproduce this crash. Once the disk gets full, kget stalls the download and I can pause and resume (start over) as much as I want without it crashing. Marking as fixed. Thanks!