--BUG DISCOVERED--Deluge 0.5.8.1 Crash [Ubuntu 7.10 64 bit]

General support for problems installing or using Deluge
Post Reply
AdemoS
New User
New User
Posts: 6
Joined: Thu Jan 17, 2008 9:17 pm

--BUG DISCOVERED--Deluge 0.5.8.1 Crash [Ubuntu 7.10 64 bit]

Post by AdemoS »

I got a crash using Ubuntu 7.10 64 bit, running Deluge 0.5.8.1 64 bit

It first crashed when I switched on Encryption to Forced for both sending and receiving. Now, after each computer restart it crashes whenever I try to start downloading, or other regular tasks.

If I try to run the program after the crash, from the Applications menu, it says "Loading Deluge" on the Application Chooser bar, but then disapears.

So I tried to launch Deluge using the terminal.

It gave me these errors:
Starting DHT...
No DHT file to resume
terminate called after throwing an instance of 'asio::system_error'
what(): Address already in use
If you need any other logs please let me know where they are located by default, and I'll paste them onto pastebin.
Last edited by AdemoS on Fri Jan 18, 2008 11:39 pm, edited 3 times in total.
Awperator
New User
New User
Posts: 3
Joined: Fri Jan 18, 2008 2:01 am

Re: Deluge 0.5.8.1 Crash [Ubuntu 7.10 64 bit]

Post by Awperator »

The what(): Address already in use error is probably because you have a zombie process in the background that needs to be killed first. I also have encryption on for sending and receiving and I have problems with it crashing after computer restarts. I'm using mythbuntu 7.10 and Deluge 0.5.8 32 bit. I'm going to disable encryption and see if it helps (and also see if I can seed better.)
AdemoS
New User
New User
Posts: 6
Joined: Thu Jan 17, 2008 9:17 pm

Re: Deluge 0.5.8.1 Crash [Ubuntu 7.10 64 bit]

Post by AdemoS »

Grr..

Well you were right, my Wicd python-based tray had turned Zombie.

I killed it and restarted.

No more zombie, but same error from Deluge.....



Any other ideas would be great. I think I may have to just reboot and turn off encryption.

EDIT: Turning off "Encyrption Forced" on both sending and receiving fixed my issue.....

There seems to be a Python bug in that feature. (since Python was usually the process that needed to be killed after)

Edit 2: Tried to file a bug report and got an error:
TICKET_CREATE privileges are required to perform this operation
Post Reply