Hi,

the following just happened:

I startet downloading a torrent with ktorrent, let it run a while, and then finished downloading with azureus.
After i restarted ktorrent, it started downloading again and showing wrong download progress values. It should instead have recognized, that the data is complete, and should have started seeding.

You need to use the import plugin for that.

I have to agree that it's a broken system though. Every other BT client checks data when doing "save as". I think it'd be better if KTorrent did it too.

I don't think it's so bad.... you just have to take into account that KTorrent want you to use the import wizard.

PS. the faq needs some helping hand on this.

I'm gonna change that, it is not really logical at the moment. I'm also going to add the option to check a download at any moment.

George wrote:I'm also going to add the option to check a download at any moment.

We have a bunch of nice features waiting to get into KTorrent, i can't wait. ( but i will, be assured, lol)

hi, i just encountered a crash with ktorrent (svn from yesterday), one file seeding, and one downloading. I started it with kdevelop in gdb and got this backtrace.

(gdb) backtrace
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6c953f3 in __write_nocancel () from /lib/tls/libpthread.so.0
#2 0xb73b5dd6 in QSocketDevice::writeBlock () from /usr/qt/3/lib/libqt-mt.so.3
#3 0xb73b291c in QSocket::flush () from /usr/qt/3/lib/libqt-mt.so.3
#4 0xb73b220a in QSocket::sn_write () from /usr/qt/3/lib/libqt-mt.so.3
#5 0xb752db0b in QSocket::qt_invoke () from /usr/qt/3/lib/libqt-mt.so.3
#6 0xb71a9ed4 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#7 0xb71aa49a in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#8 0xb74fd780 in QSocketNotifier::activated () from /usr/qt/3/lib/libqt-mt.so.3
#9 0xb71c6a7f in QSocketNotifier::event () from /usr/qt/3/lib/libqt-mt.so.3
#10 0xb714709f in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3
#11 0xb714723c in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb786ff6d in KApplication::notify () from /usr/kde/3.5/lib/libkdecore.so.4
#13 0xbff93170 in ?? ()
#14 0xb7474495 in QGList::prepend () from /usr/qt/3/lib/libqt-mt.so.3

As this looks a bit weird to me, maybe someone else can give me a hint how to debug this (have it running with gdb at the moment).

Was it a segmentation fault (SIG_SEGV) ?

The crash is in the middle of Qt code, so I doubt we will be able to do much.

Yes, AFAIR it was a SIGSEGV. I just wondered that it crashed out of the blue with the backtrace beginning in QGList::prepend.

It just happened again. Error Signal was a SIGPIPE, same backtrace.

_megaman_ wrote:It just happened again. Error Signal was a SIGPIPE, same backtrace.

The first thing KT does is ignore SIGPIPE's.

sorry, i know now whats going on. Somehow Installation of kdesvn caused kded to crash all the time with an svn::ClientException. Even when just using konqueror. Thats probably the reason for my ktorrent problems too.

That seems totally unrelated.