I see that there are progresses in the ktorrent development ,but still there are ,many error that prevent me from using it as my one and only torrent client ,the first thing is
-i donwloaded something and it stoped at 99,90% ,annoying ,isn`t it? ,and i removed the file ,and used the partialy completed downloads plugin to put it back and walla ,it was 100% completed
the second error:
-after donwload ,it didn`t began to seed it only connected to a few peers ,it didn`t notice all peers in swarm and it didn`t upload anything and they were many leechers

I didn`t have these errors in previous releases.

Version ?

George wrote:Version ?

1.2

Most problems you are seeing will be fixed in the next beta release (2.0beta1). The autoscanning of files I still need to do, but it will be in the final 2.0.

George wrote:Most problems you are seeing will be fixed in the next beta release (2.0beta1). The autoscanning of files I still need to do, but it will be in the final 2.0.

Is there a snapshot or cvs available with those fixes?

DjDarkman wrote:

George wrote:Most problems you are seeing will be fixed in the next beta release (2.0beta1). The autoscanning of files I still need to do, but it will be in the final 2.0.

Is there a snapshot or cvs available with those fixes?

Yes there is, i use it all the time
You have to download and compile to be able to install it.
The faq has these steps listed here, but you might as well wait on the beta, which if i am right will be released soon.

Complied beta ,and I get "Invalid respons" in the tracker status.

DjDarkman wrote:Complied beta ,and I get "Invalid respons" in the tracker status.

That can mean a lot.
- tracker down
- too high load on the tracker and therefore temporary forbidden
- torrent not registered with tracker anymore
- client (or version) is not on a whitelist
- ?

Look in the logfile ( ~./.kde/share/apps/ktorrent/log) for a more detailed tracker response and maybe you can find out more.

I downloaded torrents from two private trackers and they worked with azureus ,btw ,this is my ktorrent log :
Bound to port 6882
DHT: Starting on port 6881
Loading plugin searchplugin
Loading plugin infowidgetplugin
Loading plugin partfileimportplugin
Showing KT
DHT: Stopping
IP 0.0.0.0 banned.

I looks like all I needed was to change the port ,It works now ,but there are strange errors in the log like this

Code: Select all

Authentication(S) to 84.52.164.130 : failure
Timeout occured
Authentication(S) to 211.31.18.124 : failure
Weird bug detected !
Making sure everything is back OK
Cannot find PeerManager for hash : b2502a36b5fb0a306c169ba2da45edec5f1957a9

but despite these massagees in the log window ,I can download and/or upload torrents nicely ,just wanted to show this.
btw ,ktorrent gives invalid response if a tracker tells ktorrent that the port it`s using is blacklisted ,I think ktorrent should give the blacklisted port message ,so that a user who does`t watch the log would know that he has to change the port.

This was was all true ,before ktorrent crashed ,and after I restarted it ,it didn`t want to seed ,the log is big ,should mail it to someone?

DjDarkman wrote:I looks like all I needed was to change the port ,It works now ,but there are strange errors in the log like this

Yeah some trackers have reason to blacklist ports because of speed issues.

Code: Select all

Authentication(S) to 84.52.164.130 : failure
Timeout occured
Authentication(S) to 211.31.18.124 : failure
Weird bug detected !
Making sure everything is back OK
Cannot find PeerManager for hash : b2502a36b5fb0a306c169ba2da45edec5f1957a9

Believe it or not, but the
"Weird bug detected !
Making sure everything is back OK"
message is a good sign because it's a fix for getting arround a bug.

The rest of the log in code seems also legimit.

but despite these massagees in the log window ,I can download and/or upload torrents nicely ,just wanted to show this.
btw ,ktorrent gives invalid response if a tracker tells ktorrent that the port it`s using is blacklisted ,I think ktorrent should give the blacklisted port message ,so that a user who does`t watch the log would know that he has to change the port.

Would be a nice feature to have, i agree.

This was was all true ,before ktorrent crashed ,and after I restarted it ,it didn`t want to seed ,the log is big ,should mail it to someone?

Hmm, dunno. Have you tried to stop the all torrents and restart KTorrent again?

Tried everything with no luck.here is a log ,i hope it helps ,i realy want to start using ktorrent http://djdarkman.pastebin.us/412