1) Upgrading to the recent SVN's gave me the following error with several specific torrents after running for a while. About week ago this didn't happen. Torrent status column says somethink like this for those torrents:
"Error: Error: Reading past the end of the file /home/username/.kde3.5/share/apps/ktorrent/tor242/cache/"

(Yep, that's also a double "Error: Error:").

I've been seeding those torrents for months/weeks. In my opinion the only things that might have caused this are a bug in the recent SVN's of ktorrent or ktorrent crashing.

2) The recent SVN's also have a strange issue with one specific torrent, which i've been seeding for a long time. It reported the torrent as incomplete - chunk 726 (of a total of 727 chunks) was missing/damaged or something. So it started to download it again. It downloads the chunk and disregards it every time, also banning the IP's of the peers i got it from, saying "bad data received". Previously I had all data, and it was checked. And it's unlikely the other seeders have bad data.

Here's that last torrent: link. Chunk 726 is probably directories "William Reid" and "William Romaine".

3) After I uncheck these directories of the torrent previously mentioned so they won't be downloaded, the download finishes. The files tab of the infowidget of the torrent which is now seeding shows:

File | Size | Download | ...
...
> [v] William Law | 4.5 MB | Yes | ...
v [ ] William Reid | 302,2 KB | No | ...
[ ] Bloof of Jesus.rtf | 302.2 KB | No | ...
v [ ] William Romaine | 37.9 KB | Yes | ...
[ ] Self-existance of Jesus Christ.rtf | 37.9 KB | No | ...
> [v] W M Ramsay | 1.5 MB | Yes | ...
...

Shouldn't it show download=No for the William Romaine directory as it only contains one file which is not downloaded?

I will see if I can reproduce this

OK, it started downloading 726 pretty soon and when it was finished, the hash verification failed, so assuming that the data sent was OK, this is strange.

There has not been much change in this area lately.

EDIT: after taking a look at the data of said chunk, it seems to be readable text, so I think we can assume that the peers are sending correct data

OK it is fixed

Yep, it definately fixed the first 2, the more critical, bugs. Thank you!