transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| transmission (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: transmission-gtk 2.77-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-13-generic i686
ApportVersion: 2.9.2-0ubuntu2
Architecture: i386
Date: Wed Mar 20 21:12:37 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-02-25 (22 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: transmission-gtk /home/username/
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_IN
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb6cd9dc9 <curl_multi_
PC (0xb6cd9dc9) ok
source "%edx" ok
destination "(%eax)" (0x00000000) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
curl_multi_cleanup () from /usr/lib/
?? ()
?? ()
start_thread () from /lib/i386-
clone () from /lib/i386-
Title: transmission-gtk crashed with SIGSEGV in curl_multi_
UpgradeStatus: Upgraded to raring on 2013-03-09 (10 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| srikar (srikar) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-i386-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1124508, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.