Page 1 of 1

Deluge crashes since Ubuntu update

Posted: Mon Jul 08, 2013 7:00 pm
by Wcool
Hi,

Since updating my homeserver (HP Proliant Microserver 36L) with standard updates from Canonical I have troubles with Deluge.
I run deluge-ui and it started to crash randomly but normally within 3 minutes. It also crashes a lot more if there is more than 1 torrent downloading.

If there is only 1 stream downloading and I put all the rest on pause, it often works but not always.

It's quit frustrating, does anyone else have the same problem?

Some info:
uname -a
Linux pepper 3.2.0-48-generic #74-Ubuntu SMP Thu Jun 6 19:43:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

apport.log:
ERROR: apport (pid 3114) Mon Jul 8 19:39:18 2013: called for pid 3089, signal 11
ERROR: apport (pid 3114) Mon Jul 8 19:39:18 2013: script: /usr/bin/deluge, interpreted by /usr/bin/python2.7 (command line "/usr/bin/python /usr/bin/deluge")
ERROR: apport (pid 3114) Mon Jul 8 19:39:18 2013: gdbus call failed, cannot determine running session: [Errno 2] No such file or directory
ERROR: apport (pid 3114) Mon Jul 8 19:39:20 2013: this executable already crashed 2 times, ignoring

kern.log
Jul 8 19:39:18 pepper kernel: [ 458.687053] deluge[3098]: segfault at 3192000 ip 00007f50d3a3e746 sp 00007f50bfffdfa0 error 4 in libcrypto.so.1.0.0[7f50d39b5000+1b1000]

Anyone any idea?

Thanks,

Jeroen

Re: Deluge crashes since Ubuntu update

Posted: Tue Jul 09, 2013 10:53 am
by Wcool
Interesting, further analysis and experimenting suggests it might not be related to the Ubuntu update but a specific torrent.
It looks like I have no problem if I set a certain torrent in the queue to Paused.

Could there be some malicious peers out there that deliberately make lib crypto crash?

Re: Deluge crashes since Ubuntu update

Posted: Tue Jul 09, 2013 10:58 am
by Cas
There is an issue in libcrypt, search for more details.

Re: Deluge crashes since Ubuntu update

Posted: Tue Jul 09, 2013 2:53 pm
by Wcool
Thanks for that, it seems many people have the same issue.

For instance: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705218

I will see if I can find a workaround