wifi crash with feisty + 3.4-1

[fickschnell]

Why hello there!

I'm running deluge 3.4-1 via gui on feisty ubuntu and have had this problem where when I begin a torrent download, deluge finds a few peers, then crashes. This not only crashes deluge, but also crashes my wifi, which I connect to via wicd. The only way I can get wicd up and running again is to reboot. Any suggestions? Please let me know if there's more info I can send.

Thanks....

[markybob]

Why hello there!

I'm running deluge 3.4-1 via gui on feisty ubuntu and have had this problem where when I begin a torrent download, deluge finds a few peers, then crashes. This not only crashes deluge, but also crashes my wifi, which I connect to via wicd. The only way I can get wicd up and running again is to reboot. Any suggestions? Please let me know if there's more info I can send.

Thanks....

i dont know what you mean by 3.4-1, but try deluge 0.5.4.1 that was released a few minutes ago

[fickschnell]

whoa, yeah, that was some crazy typing on my part....sorry. I'll give the new version a try. Thanks!

[fickschnell]

hmmm...unfortunately the new version gives me the same problem. I get the tracker announcement, I get a list of the files in the torrent, I see 1 peer (when there are several seeders out there) and then all crashes--deluge and wicd both. This is true of multiple torrents I've tried to download, so it's not a torrent specific issue. I'm new to this world, so this is almost certainly something I'm doing wrong, but I don't know where to start or what info would be useful. I can tell you that bittorrent doesn't work for me either, though it doesn't crash wicd the way deluge does. Help?

thanks

ps again, i'm using feisty

[hypermute]

I had similar problems on a wired DSL connection. After I started Deluge, i could not browse the web anymore or download anything etc... The connection was lost, although the network manager did not realize this. After I rebooted my Ubuntu machine, everything was fine until I started Deluge.

Somewhere on the net I read that this might have something to do with the maximum tcp connections, which the router may not be able to cope with. They're now limited to 75 and my connection does not screw up anymore.

yours,
hypermute

[Ubuntu Feisty, FRITZ!Box Fon WLAN 7050, Deluge 0.5.4.1 feisty deb]

[stylius]

Same problem here. It took me two days to realize that Deluge caused the connection hangups. Afterwards I must reboot or force restart the whole networking to be able to connect again.

I am using Ubuntu Feisty, kernel 2.6.20-16-generic, Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (bcm43xx firmware). The Deluge version is 0.5.4.

If I remember correctly, the 0.5.2 version did not have that problem. I will give a try to the new 0.5.4-1, but if it keeps on crashing, I'll downgrade to 0.5.2

EDIT:

Yup, still buggy. I downloaded older version (0.5.2) from http://www.getdeb.net. Hope to keep my connection longer

[fickschnell]

so should this be posted as a bug somewhere? Forgive me if I missed the right place to post...

[stylius]

Here is a possible fix. My connection never crushed since I changed the initial handshake connection speed from 2048 to 512. Here is what i did:

I downloaded latest svn version (Take a look at Development Page for more info). A folder "deluge" was created at my home folder. I then edited bt_peer_connection source file:

Code: Select all

sudo gedit ~/deluge/libtorrent/src/bt_peer_connection.cpp

I changed lines 159 and 160. Here is a copy before and after change:

m_bandwidth_limit[download_channel].assign(2048);
m_bandwidth_limit[upload_channel].assign(2048);

m_bandwidth_limit[download_channel].assign(512);
m_bandwidth_limit[upload_channel].assign(512);

And then I compiled it.
I am not sure if the latest svn version fixed that or it was the lowering ot the initial handshake connection speed. The fact is it works for me now, without crash for almost two days.

[stylius]

Well, it was a 3 day miracle! It now crashes again. Any Ideas?

[SNWBRDR]

Having the exact same problem.
Only, I don't have to reboot, just wait a minute till the connection is back after closing (force quit mostly) Deluge.
Lowering the amount of connections doesn't help.