I have noticed a problem with Ktorrent..

I usually use uTorrent but I wanted to try out Ktorrent so I created a torrent with uTorrent uploaded it to a tracker and waited for some leechers. The torrent was being upped pretty slowly in uTorrent in over 24 hours it onlu upped about 15 MB. Anyway I thought I'd fire up Ktorrent added the torrent and it immediately shot up to my max upload and listed 3 leechers. I closed uTorrent and waited about 15 mins or so and when I checked the tracker site it says that there are no seeds however in Ktorrent it is seeding to 4 leechers and getting some good speeds. My auestion is, why is it doing this? I can't build my ratio because my uploads aren't being accepted because the tracker says there's no seeds on the torrent however Ktorrent says otherwise. Any ideas?

How read this, you were seeding the same torrent at the same time on two clients. You should never ever do that, because the tracker doesn't speak that language. This is probably where to the problem started too:

twice event started-> one event stopped (got you off the seeders list and removed your active flag)-> you keep seeding in another client while the tracker thinks you stopped

No you misunderstood., I wasn't running both at the same time. I was using Ktorrent.I actually uploaded all day yesterday using Ktorrent no other applications open and my ratio never went up once. What a waste because when you are trying to improve your ratio it dosen't help if it's not reporting to the tracker correctly..

Yeah the chance this problem was caused by above thing was small anyway, seeing that most trackers have a limit of one connection on a single torrent.

What tracker are we talking about?

First, Thejinx, did you use the import plugin ?

According to the spec
http://wiki.theory.org/BitTorrentSpecif ... S_Protocol

event: If specified, must be one of started, completed, stopped, (or empty which is the same as not being specified). If not specified, then this request is one performed at regular intervals.
started: The first request to the tracker must include the event key with this value.
stopped: Must be sent to the tracker if the client is shutting down gracefully.
completed: Must be sent to the tracker when the download completes. However, must not be sent if the download was already 100% complete when the client started. Presumably, this is to allow the tracker to increment the "completed downloads" metric based soley on this event.

If you used the import plugin, KT will not send the completed event, which is the correct behavior.

If you used the auto import (so you just opened a torrent and KT found the files in the download location), then KT screws up and sends both a started and completed event.

Stoeptegel reported this bug, and I still need to fix it :
https://bugs.kde.org/show_bug.cgi?id=132066