Hello mates.

I am a new user of KTorrent under Ubuntu Jaunty 9.04. These two days made me realize that KTorrent is the torrent client I need (despite just a couple of features missing). Today I updated from the one which was in the Ubuntu repositories (3.1.something) to the latest 3.2.4. This package was compiled with all dependencies satisfied by the maintainer of the 4.3 trunk of KDE for Ubuntu until Karmic is released. The program works fine, but now all my torrents say, in the status of communication with the tracker (private tracker btw) "The process for the <trackerurl> protocol died unexpectedly". The thing is that I'm still being able to seed and download from the private tracker, but my stats in the tracker don't change.

I searched in the bug db but nothing I found helped me. Any clues of what's happening, and how to solve it?

Thanks in advance, and congrats for such a good program.

Regards, Pi

Disregard the previous message. I fixed it by disabling KIO. I don't know what it is, it seems that it's a library to process certain protocols instead of using KTorrent's internal code. The curious thing was that I was getting one torrent from another tracker (also private) but with that one there were no errors. Does that mean that KIO has a bug, or that the tracker which gave me the errors was giving me malformed data? I want to know because if it's the second, I want to warn the staff to fix that data, and if it's the former... Well, I think KIO already has one bug pertaining that.

It's a bug in the tracker, they are sending back bad http, KIO (which is the KDE library we use to do tracker announces) is a bit to strict. So we have added a less strict implementation of the http protocol.

Can you name a few torrent clients which use the KIO library? Or is KTorrent the only KDE torrent client?

I have no idea what KMLDonkey uses, and as far as I know, that is the only other KDE based torrent client.

kget

sek.tor wrote:kget

kget uses KTorrent btcore.

I did not know that kget uses the ktorrent btcore and also kmldonkey.
It's bug in tracking after update. You are not using the strict http protocol.
It works fine. New release will continuously updating the software.