George wrote:It has been committed in revision 973256 (trunk only at the moment, still needs to be backported to stable)

Disabling KIO is done in Advanced Settings -> Miscellaneous

Proxy settings should keep on working.

The tracker announce message in the log has been slightly changed and now shows what is being used :

Doing tracker request to url (via QHttp) : http://tracker.com/announce?... (new way)
Doing tracker request to url (via KIO) : http://tracker.com/announce?... (old way)

It is working for me!

With stable version I wasn't able to download from 2-3 certain private trackers and now everything OK (ktorrent-svn-973256)

George wrote:It has been committed in revision 973256 (trunk only at the moment, still needs to be backported to stable)

Disabling KIO is done in Advanced Settings -> Miscellaneous

Proxy settings should keep on working.

The tracker announce message in the log has been slightly changed and now shows what is being used :

Doing tracker request to url (via QHttp) : http://tracker.com/announce?... (new way)
Doing tracker request to url (via KIO) : http://tracker.com/announce?... (old way)

It's great to see that this has been fixed! This has been a very irritating bug. Ktorrent still works with it, but nowhere near as well.

When are you currently planning to put out 3.2.2? I don't want to be pushy or anything (put it out whenever makes the most sense for you), but this bug has made using ktorrent considerably less pleasant and I'd really like to have the fix in an official release as opposed to just svn. So, I'm just wondering what the timeframe is for the next bugfix release. Can we expect it in the next week or two or do we really need to use the svn version if we want to have this fix anytime soon?

Kalessin wrote:

George wrote:It has been committed in revision 973256 (trunk only at the moment, still needs to be backported to stable)

Disabling KIO is done in Advanced Settings -> Miscellaneous

Proxy settings should keep on working.

The tracker announce message in the log has been slightly changed and now shows what is being used :

Doing tracker request to url (via QHttp) : http://tracker.com/announce?... (new way)
Doing tracker request to url (via KIO) : http://tracker.com/announce?... (old way)

It's great to see that this has been fixed! This has been a very irritating bug. Ktorrent still works with it, but nowhere near as well.

When are you currently planning to put out 3.2.2? I don't want to be pushy or anything (put it out whenever makes the most sense for you), but this bug has made using ktorrent considerably less pleasant and I'd really like to have the fix in an official release as opposed to just svn. So, I'm just wondering what the timeframe is for the next bugfix release. Can we expect it in the next week or two or do we really need to use the svn version if we want to have this fix anytime soon?

The release is planned for today (unless something serious comes up, but that is unlikely)

George wrote:

Kalessin wrote:

George wrote:It has been committed in revision 973256 (trunk only at the moment, still needs to be backported to stable)

Disabling KIO is done in Advanced Settings -> Miscellaneous

Proxy settings should keep on working.

The tracker announce message in the log has been slightly changed and now shows what is being used :

Doing tracker request to url (via QHttp) : http://tracker.com/announce?... (new way)
Doing tracker request to url (via KIO) : http://tracker.com/announce?... (old way)

It's great to see that this has been fixed! This has been a very irritating bug. Ktorrent still works with it, but nowhere near as well.

When are you currently planning to put out 3.2.2? I don't want to be pushy or anything (put it out whenever makes the most sense for you), but this bug has made using ktorrent considerably less pleasant and I'd really like to have the fix in an official release as opposed to just svn. So, I'm just wondering what the timeframe is for the next bugfix release. Can we expect it in the next week or two or do we really need to use the svn version if we want to have this fix anytime soon?

The release is planned for today (unless something serious comes up, but that is unlikely)

Great to hear. Hopefully Gentoo's ebuild won't be far behind.

Thanks for all your hard work, and may ktorrent continue to be great.

Code: Select all

Index: libbtcore/tracker/httpannouncejob.cpp
===================================================================
--- libbtcore/tracker/httpannouncejob.cpp       (revision 976228)
+++ libbtcore/tracker/httpannouncejob.cpp       (working copy)
@@ -35,7 +35,7 @@

        void HTTPAnnounceJob::start()
        {
-               http->setHost(url.host(),url.protocol() == "https" ? QHttp::ConnectionModeHttps : QHttp::ConnectionModeHttp,url.port());
+               http->setHost(url.host(),url.protocol() == "https" ? QHttp::ConnectionModeHttps : QHttp::ConnectionModeHttp,url.port() > 0 ? url.port() : 0);
                if (!proxy_host.isEmpty() && proxy_port > 0)
                        http->setProxy(proxy_host,proxy_port);

@@ -90,4 +90,4 @@



-}
\ No newline at end of file
+}

is needed. url.port() returns -1 if the port isn't specified which results into 65535 port when passed as unsigned value to setHost()

You are right, will fix that before release

George wrote:You are right, will fix that before release

George, your fix in trunk is wrong with regard to https. There is the reason I did the patch that way. setHost() will choose the right port according to protocol if 0 is passed.

It is unfortunate you released 3.2.2 with that bug...

MoDaX wrote:It is unfortunate you released 3.2.2 with that bug...

Gonna update the package soon with a fix for this

OK, a new package has been uploaded :

http://ktorrent.org/downloads/3.2.2/ktorrent-3.2.2-1.tar.bz2

Is the 'Stalled' bug supposed to be fixed in 3.2.2 or should I try 3.2.2-1, because I have it quite often in 3.2.2 from gentoo portage.

prizident wrote:Is the 'Stalled' bug supposed to be fixed in 3.2.2 or should I try 3.2.2-1, because I have it quite often in 3.2.2 from gentoo portage.

Disable KIO for tracker announces (advanced settings). 3.2.2 should work unless your torrent uses https URL without explicit port. Then you need 3.2.2-1.

George wrote:It has been committed in revision 973256 (trunk only at the moment, still needs to be backported to stable)

Disabling KIO is done in Advanced Settings -> Miscellaneous

Proxy settings should keep on working.

The tracker announce message in the log has been slightly changed and now shows what is being used :

Doing tracker request to url (via QHttp) : http://tracker.com/announce?... (new way)
Doing tracker request to url (via KIO) : http://tracker.com/announce?... (old way)

Thank you for the tip.

I've disabled KIO in KTorrent 3.2.2, KDE 4.2.4 (Fedora 11) with noticeable results.

Oddly enough Ktorrent 3.2.1, KDE 4.2.95, Kubuntu 9:04 continues to perform better for me at least.

Perhaps some of the changes made in the later KDE have helped out here?

I'm still experiencing speed problems though, (3.2.2 on Fedora 11), and not only with low seed / leach torrents.

For example a torrent I currently downloading has 96 seeds and 32 leachers. of which I am connected to 23 seeds and 12 leachers.

These connections do fluctuate but not by much.

Yet the download rate rarely exceeds 6kbs.

Any suggestions would be most welcome.

Could the issue mentioned below be a contributing factor?

Non_E wrote:

BigJim wrote:I got "Invalid response from tracker" when trying to access open.tracker.thepiratebay.org, then noticed KTorrent was reaching it via IPv6 and changed it to prefer IPv4, which instantly worked.

Yes! That is definitely the problem I have. Still, could someone help me how do I set ktorrent to prefer ipv4 without disabling ipv6 entirely?

Cheers.