Totay I've found, that latest revisions don't send to tracker event=completed when closing KTorrent.
Manually stopping torrents works fine.


And maybe small request
Some confirmation dialog when deleting torrent from list. Today I missclicked stop button and deleted one torrent. It took me some time, to add it again

It shouldn't send event=completed because we quit client/stop torrent, you probably meant an announce with event=stopped.

The request is not for me to reply

stoeptegel wrote:It shouldn't send event=completed because we quit client/stop torrent, you probably meant an announce with event=stopped.

Sorry, my bad. I meant, that there's nothing announced to the tracker, and it still thinks, that I'm seeding.

Normally we should allow enough time to send a stopped event to the tracker to the tracker at exit But we can't wait forever of course.

I'll check this out.

I have done some tests and the stopped events do appear to get through.

I currentlly have 14 torrents running in KTorrent. Checked with ethereal - in few attempts Ktorrent send only 6 - 9 event=stopped.

I think KT should wait until all events will be sent, to report tracker right info.

That's not good, of course we cannot wait forever, but if the tracker is responsive it should get through.