transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()

[George Bahry]

Transmission doesn't load .torrent files properly. Any .torrent file shows up as empty and no download is added to the queue (tested with Ubuntu 12.04.2 torrents and Ubuntu 11.04 torrents).

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: transmission-gtk 2.76-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 14 22:30:16 2013
ExecutablePath: /usr/bin/transmission-gtk
InstallationDate: Installed on 2013-02-02 (13 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130201.1)
MarkForUpload: True
ProcCmdline: transmission-gtk /home/username/Downloads/ubuntu-12.04.2-desktop-i386.iso.torrent
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd2b8ea85a0 <curl_multi_cleanup+176>: mov %rax,(%rdi)
 PC (0x7fd2b8ea85a0) 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 libvirtd lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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.