transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()

[Aleksey]

!

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: transmission-gtk 2.77-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Sat Mar 23 15:28:46 2013
ExecutablePath: /usr/bin/transmission-gtk
InstallationDate: Installed on 2013-03-21 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130321)
MarkForUpload: True
ProcCmdline: transmission-gtk
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd9abfc15a0 <curl_multi_cleanup+176>: mov %rax,(%rdi)
 PC (0x7fd9abfc15a0) 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
XsessionErrors:
 (gnome-control-center:1847): gnome-control-center-unity-WARNING **: Could not load /usr/share/themes/Adwaita/index.theme: Нет такого файла или каталога
 (gnome-control-center:1847): Gtk-CRITICAL **: gtk_builder_get_object: assertion `GTK_IS_BUILDER (builder)' failed
 (gnome-control-center:1847): Gtk-CRITICAL **: gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' failed

[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.