Jump to content

2248 Doesn't Download on Linux


Computer Guru

Recommended Posts

Under Wine 2248 does establish connections to other users.

I have a green status bar, the torrent has 3000 seeds and 1000 leeches (VERY healthy!) and downloads at full speed with 2248 under Vista. But on Linux it refuses to establish connections to peers, though all 8 trackers connect just fine.

No upload, no download.

Tested with multiple torrents.

Technically it "connects" .... to one or two peers, zero seeds. Uploads at 0.2kbps (though the torrent is 50% complete and 4GB total)

Kept running for 4 hours: dl at 0.1kbps ul at 0.2kbps when I checked. Graph is virtually nil the whole time.

Could the dl/ul limit fix that is in other threads have broken socket access in Wine?

Testing with 2228..... Nope, same there.

[23:35:25]  86.152.199.74   : Disconnect: Timed out
[23:35:25] 86.140.132.110 : Disconnect: Timed out
[23:35:25] 201.14.140.203 : Disconnect: Timed out
[23:35:25] 76.171.184.116 : Disconnect: Timed out
[23:35:25] 77.96.77.31 : Disconnect: Timed out
[23:35:25] 76.171.21.231 : Disconnect: Timed out
[23:35:25] 84.81.147.2 : Disconnect: Timed out
[23:35:25] 86.140.132.110 : Connecting: port 14228 source: T
[23:35:25] 86.152.199.74 : Connecting: port 53126 source: T
[23:35:25] 71.179.21.187 : Connecting: port 14769 source: T
[23:35:25] 71.168.143.67 : Connecting: port 29314 source: T
[23:35:25] 71.158.164.235 : Connecting: port 44261 source: T
[23:35:25] 71.125.65.57 : Connecting: port 16480 source: T
[23:35:25] 71.106.157.200 : Connecting: port 8952 source: T
[23:35:26] 75.6.165.109 : Disconnect: Peer error: offline (timed out)
[23:35:26] 83.226.212.144 : Disconnect: Timed out
[23:35:26] 75.17.59.181 : Disconnect: Peer error: offline (timed out)
[23:35:26] 71.126.3.19 : Disconnect: Timed out
[23:35:26] 84.104.4.240 : Disconnect: Timed out
[23:35:26] 86.132.196.111 : Disconnect: Peer error: offline (timed out)
[23:35:26] 86.97.170.185 : Disconnect: Peer error: offline (timed out)
[23:35:26] 81.225.33.45 : Disconnect: Peer error: offline (timed out)
[23:35:26] 71.197.253.68 : Connecting: port 17398 source: H
[23:35:26] 71.126.3.19 : Connecting: port 52785 source: H
[23:35:26] 150.101.169.57 : Connecting: port 19000 source: H
[23:35:26] 217.165.7.248 : Connecting: port 9040 source: H
[23:35:26] 74.98.137.230 : Connecting: port 49123 source: H
[23:35:26] 91.10.67.87 : Connecting: port 10601 source: H
[23:35:26] 90.192.167.16 : Connecting: port 20266 source: T
[23:35:26] 90.195.36.119 : Connecting: port 16310 source: T
[23:35:26] Incoming connection from 89.168.73.252
[23:35:26] 89.168.73.252 : Disconnect: Too many global conns
[23:35:27] 88.118.156.171 : Disconnect: Peer error: offline (timed out)
[23:35:27] 74.13.180.212 : Disconnect: Peer error: offline (timed out)
[23:35:27] 90.199.179.200 : Connecting: port 6881 source: T
[23:35:28] 88.207.62.208 : Disconnect: Peer error: offline (timed out)
[23:35:28] 68.192.45.204 : Disconnect: Timed out
[23:35:28] 86.129.116.37 : Disconnect: Peer error: offline (timed out)
[23:35:28] 89.212.48.145 : Disconnect: Timed out
[23:35:28] 85.138.236.217 : Disconnect: Peer error: offline (timed out)
[23:35:28] 82.41.59.35 : Disconnect: Timed out
[23:35:28] 80.177.103.245 : Disconnect: Timed out
[23:35:28] 80.177.103.245 : Connecting: port 25089 source: H
[23:35:28] 82.41.59.35 : Connecting: port 64250 source: H
[23:35:28] 89.212.48.145 : Connecting: port 52188 source: H
[23:35:28] 68.192.45.204 : Connecting: port 40048 source: H
[23:35:28] 221.221.142.36 : Connecting: port 58794 source: H
[23:35:28] 83.108.161.74 : Connecting: port 16949 source: H
[23:35:28] 76.64.96.87 : Connecting: port 15401 source: H
[23:35:29] 84.104.227.127 : Disconnect: Timed out
[23:35:29] 82.40.189.23 : Disconnect: Timed out
[23:35:29] 89.220.85.222 : Disconnect: Peer error: offline (timed out)
[23:35:29] 72.161.117.116 : Disconnect: Peer error: offline (timed out)
[23:35:29] 72.174.66.10 : Disconnect: Peer error: offline (timed out)

Going to try it with the build before 2228 (if i can get my hands on it).

EDIT:

Bug was introduced in 2224. Had to go all the way back to 2151 to circumvent.

Basically, it ceeps connecting to peers and thinking they're offline. Can't see anything in the 2224 changelog to indicate this behavior though....

Link to comment
Share on other sites

I am compiling 0.9.38 now as there is no .deb available for Etch as I type this.

Will report back.

EDIT:

Turned out it was more bother than it was worth to compile manually just to get utorrent to work. I will wait for .debs then report back.

Link to comment
Share on other sites

Seeing as utorrent is the only app I use under wine I deleted my ~/.wine folder and reinstalled the 0.9.37 deb but I still had the same results with the 1.7 2248 beta. Not only that but when I downgraded back to 2151 that no longer worked and exhibited the same symptoms as 2248.

So now I am using 1.61 and will await the next beta to test again.

Link to comment
Share on other sites

:S

I mean, this is definitely a bug introduced in the recent builds that manifests itself on Linux.... but what's the kicker?

I'm going to try to disable various options (like encryption, UPnP, etc.) and see if it makes a difference.

EDIT:

No go. Nothing makes a difference :@

Link to comment
Share on other sites

Everything worked out of the box here... I just did a clean install of Ubuntu 7.04 on a virtual machine, installed the updates along with Wine, grabbed a copy of build 2248, ran it with Wine, and downloaded the OOo torrent. Worked :|

Link to comment
Share on other sites

Nope.

Figured it out, though I don't understand it.

Deleting settings.dat and recreating it from scratch didn't help.

Deleting resume.dat and recreating it from scratch didn't help.

Deleting both at once and having both recreated from scratch worked.

There is a bug in uTorrent only on Linux that won't download existing or new entries if using an old configuration file.

I guess you can close this thread, but anyone upgrading from uTorrent 1.6 to 1.7 (whenever it comes out) and using Linux will have to lose all of his/her settings to make uTorrent work.

Link to comment
Share on other sites

screenshot2151bx0.th.png screenshot2248ft2.th.png screenshot2448lh9.th.png

Not at all. I started with cleared settings, and installed build 2151. After downloading for a bit, I upgraded directly to 2248. Still worked. Just to be sure, I upgraded to 2448, and it worked. I see nothing wrong with µTorrent under Wine -- at least nothing that you've been describing as of late. And just to be sure, you can ignore the fact that settings.dat is located in the same directory as the executable, as I tried it both ways (encapsulated install and normal %appdata%\uTorrent install).

Another Wine bug worth noting, though (after looking over my screenshots) is that the y-axis label isn't drawn properly. Under Windows, µTorrent writes it vertically, but I guess Wine doesn't implement that.

Link to comment
Share on other sites

Maybe my post will not be very useful, but i need to add, that under my Ubuntu Feisty Fawn 7.04 installation, uTorrent betas works perfectly, no problems at all.

Now I'm using wine-0.9.38 and uTorrent 1.7 2465, but even with earlier versions of wine and uTorrent betas I didn't have any problems.

UPnP, NAT-PNP, and Windows Firewall exception is unchecked. That's the only changes I've made in uTorrent network related settings.

Link to comment
Share on other sites

I am having similar symptoms myself too...

Ubunty 7.04, wine 0.9.38.

While uTorrent 1.6.1 works fast as ever, any recent 1.7 betas basically doesn't download anything. While there is torrent which has say 1000 seeds, it eventually came, but like few kilobytes/sec, and then some torrent with say 30 seedes it virtually never comes. uTorrent sees the seeders and leechers etc, but virtually nothign ever downloads...

Link to comment
Share on other sites

µTorrent still hasn't *not* worked for me after testing several more times, but after relooking at my screenshots up above, I realized that my speeds in the builds following 2151 were sorely lacking, and weren't ramping up as fast as 2151 did... So yah, alus seems to have fixed the slow speeds for the next build, so hopefully, that'll fix your problems too...

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...