deluge-gtk crashed with SIGSEGV in RC4()

Bug #1232311 reported by claw on 2013-09-28
44
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Deluge
Unknown
Unknown
deluge (Ubuntu)
Undecided
Unassigned
libtorrent-rasterbar (Ubuntu)
Undecided
Unassigned

Bug Description

This was logged in #973741 and was "fixed" in an update to openssl/libcrypto as part of 12.04.2. However, the regression still exists on 64-bit Intel. It has existed in Ubuntu 12.04 LTS for some time. The fact that apport (by default) is configured on LTS to not upload crash reports, has been the only reason why I have not been able to file this report earlier.

Deluge keeps segfaulting very frequently upto 5 times within a minute, but more noticeable and likely when seeding torrents.

I know this is logged in the crash report I've uploaded, but I'll provide the information again:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise

$ apt-cache policy deluge-gtk
deluge-gtk:
  Installed: 1.3.5-0ubuntu2~precise2
  Candidate: 1.3.5-0ubuntu2~precise2
  Version table:
 *** 1.3.5-0ubuntu2~precise2 0
        500 http://au.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     1.3.5-0ubuntu1 0
        500 http://au.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
$ apt-cache policy openssl
openssl:
  Installed: 1.0.1-4ubuntu5.10
  Candidate: 1.0.1-4ubuntu5.10
  Version table:
 *** 1.0.1-4ubuntu5.10 0
        500 http://au.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1.0.1-4ubuntu3 0
        500 http://au.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
$ apt-cache policy libssl1.0.0
libssl1.0.0:
  Installed: 1.0.1-4ubuntu5.10
  Candidate: 1.0.1-4ubuntu5.10
  Version table:
 *** 1.0.1-4ubuntu5.10 0
        500 http://au.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1.0.1-4ubuntu3 0
        500 http://au.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: deluge-gtk 1.3.5-0ubuntu2~precise2
ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50
Uname: Linux 3.2.0-53-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 27 23:23:37 2013
ExecutablePath: /usr/bin/deluge-gtk
ExecutableTimestamp: 1350018898
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/deluge-gtk
ProcCwd: /home/clawrence/Personal/Downloads
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, user)
 LANG=en_AU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f586983d79e <RC4+478>: xor (%r12),%dl
 PC (0x7f586983d79e) ok
 source "(%r12)" (0x38d59ce0) not located in a known VMA region (needed readable region)!
 destination "%dl" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: deluge
Stacktrace:
 #0 0x00007f586983d79e in RC4 () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 RC4 () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
 ?? ()
Title: deluge-gtk crashed with SIGSEGV in RC4()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

claw (claw-111) wrote :

Stacktrace:
 #0 RC4 () at rc4-x86_64.s:154
 No locals.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0 RC4 () at rc4-x86_64.s:154
   [Error: rc4-x86_64.s was not found in source tree]
 #1 0x0000000000000000 in ?? ()
StacktraceTop:
 RC4 () at rc4-x86_64.s:154
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
information type: Private → Public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in deluge (Ubuntu):
status: New → Confirmed
mmalmeida (mmalmeida) wrote :

I have been experiencing the same problem in deluged - frequent crashes (every few hours).
What I've found:

1) No log written (currnelty in DEBUG )
2) I have crash reports in /var/crash/*
3) When I had access to the Unitiy interface, I saw that the apport report talked about a RC4 () SEGFAULT and mentioned libcrypto.

*Which I'd add to this report right now, if I knew how to work with apport-collect or ubuntu-bug via the command line only

mmalmeida (mmalmeida) wrote :

Follow up:

After reading that this might have been fixed in version 0.16.x of libcrypto, I have currently performed these steps:

1) Upgraded libtorrent to 0.16.11, from the PPA https://launchpad.net/~surfernsk/+archive/internet-software [1]
2) Installed the package python-libtorrent, so that deluge uses the 0.16.x version of the library
3) Currently running the deluge daemon. Will report back on the frequency of crashes.

[1] As the official repositories don't have version 0.16.x of the library in 12.04 Precise

mmalmeida (mmalmeida) wrote :

I am happy to announce that since my previous message deluge has not crashed.

This is a strong indication that there was a bug in version 0.15.x of libcrypto, which was corrected in 0.16.x.

Since Ubuntu 12.04 is an LTE, I strongly suggest that it updates to version 0.16 so that users don't get stranded with a broken version.

mmalmeida (mmalmeida) wrote :

edit: In my previous I meant libtorrent 0.16, not libcrypto

claw (claw-111) wrote :

Did you mean python-libtorrent>=0.16 instead?

Cas (calumlind) on 2014-07-21
Changed in libtorrent-rasterbar (Ubuntu):
status: New → Confirmed
Changed in deluge (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.