transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()

[wgroiss]

I downloaded a torrent-file (http://www.stresslinux.org/sl/downloads/55.torrent). After downloading => double-click. => transmission crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: transmission-gtk 2.82-1.1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 27 22:10:52 2014
ExecutablePath: /usr/bin/transmission-gtk
InstallationDate: Installed on 2013-12-29 (149 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: transmission-gtk /home/username/Downloads/stresslinux/stresslinux_64bit_11.4.x86_64-0.7.106.iso.bz2.torrent
SegvAnalysis:
 Segfault happened at: 0x7fbd40a8fb19 <gnutls_x509_crt_import+25>: mov (%rsi),%rsi
 PC (0x7fbd40a8fb19) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 gnutls_x509_crt_import () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26
 ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
Title: transmission-gtk crashed with SIGSEGV in gnutls_x509_crt_import()
UpgradeStatus: Upgraded to trusty on 2014-03-30 (57 days ago)
UserGroups: adm cdrom dip 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 #1304004, 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.