Version: v0.8.3 (using KDE 3.1.0) Installed from: (3.0) Compiler: gcc version 2.95.4 20011002 (Debian prerelease) OS: Linux When downloading the .iso images from http://www.phy.olemiss.edu/debian-cd/ via konqueror, I mark them up as queued. Then one starts downloading. When I highlight the one currently downloading, and do Transfer->Move To End, it reproducibly produces the *** KGet got signal 11 message. I'm running Debian testing as of 2003-2-18, with kde from deb http://download.us.kde.org/pub/kde/stable/latest/Debian/ stable main updated as of the same date. If you need more info to repro this, let me know. Very nice work on Kget.
Indeed. Backtrace here: (gdb) bt #0 0x00000011 in ?? () #1 0x0807586b in Transfer::slotProcessedSize(unsigned long) () #2 0x40a0a8ca in QObject::event(QEvent*) () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #3 0x40a3df12 in QWidget::event(QEvent*) () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #4 0x40ae197b in QMainWindow::event(QEvent*) () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #5 0x409b0f12 in QApplication::internalNotify(QObject*, QEvent*) () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #6 0x409b0b02 in QApplication::notify(QObject*, QEvent*) () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #7 0x406246a9 in KApplication::notify(QObject*, QEvent*) () from /opt/kde3/lib/libkdecore.so.4 #8 0x409b1cde in QApplication::sendPostedEvents(QObject*, int) () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #9 0x409b1b4c in QApplication::sendPostedEvents() () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #10 0x4096c54e in QEventLoop::processEvents(unsigned) () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #11 0x409c3dcb in QEventLoop::enterLoop() () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #12 0x409c3c74 in QEventLoop::exec() () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3 #13 0x409b1160 in QApplication::exec() () from /home/gis/src/kde/qt-copy3/lib/libqt-mt.so.3
I haven't looked at the code, but the only time I've seen this kind of problem is when items are deleted from a list, and the list is walked from lowest to highest index -- then the final item(s) in the list no longer have valid indices. I've gotten around this problem in my own code by walking lists like this in reverse order (from highest to lowest indices). Of course, it could be a different issue. Sorry I didn't click on the 'backtrace' tab myself; so enthralled with the rest of kde 3.1 that I sort of didn't think to notice it once I reproduced the crash.
Subject: kdenetwork/kget CVS commit by pfeiffer: - This should fix the crash when moving a running transfer to the end or beginning of the list - cleanup CCMAIL: 54829-close@bugs.kde.org M +65 -58 slave.cpp 1.20 M +6 -10 slave.h 1.15 M +20 -13 transfer.cpp 1.44 M +6 -6 transfer.h 1.20 M +4 -3 transferlist.cpp 1.22