transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()

Bug #1133086 reported by Сергей Иванников
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
New
Undecided
Сергей Иванников

Bug Description

transmission 2.77

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: transmission-gtk 2.77-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Tue Feb 26 08:04:53 2013
ExecutablePath: /usr/bin/transmission-gtk
MarkForUpload: True
ProcCmdline: transmission-gtk
ProcEnviron:
 LANGUAGE=ru:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f349579c5a0 <curl_multi_cleanup+176>: mov %rax,(%rdi)
 PC (0x7f349579c5a0) ok
 source "%rax" ok
 destination "(%rdi)" (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/x86_64-linux-gnu/libcurl-gnutls.so.4
 ?? ()
 ?? ()
 start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
 clone () from /lib/x86_64-linux-gnu/libc.so.6
Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Сергей Иванников (ivannixs) wrote :
Changed in transmission (Ubuntu):
assignee: nobody → Сергей Иванников (ivannixs)
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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