Bug 990176

Summary: [abrt] transmission-gtk-2.80-2.fc19: Curl_freeset: Process /usr/bin/transmission-gtk was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Antonio Guzmán Simón <aguzmansimon>
Component: transmissionAssignee: Rahul Sundaram <metherid>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: abdulkarimmemon, charles, jspaleta, kumarpraveen.nitdgp, metherid, raghusiddarth, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:100d12ff484f5e73100f97724d85c3cef88ab0d1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 16:27:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps none

Description Antonio Guzmán Simón 2013-07-30 14:03:52 UTC
Version-Release number of selected component:
transmission-gtk-2.80-2.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        transmission-gtk
crash_function: Curl_freeset
executable:     /usr/bin/transmission-gtk
kernel:         3.9.9-302.fc19.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Jul 22 14:46:54 sobremesa abrt[6796]: Saved core dump of pid 2610 (/usr/bin/transmission-gtk) to /var/tmp/abrt/ccpp-2013-07-22-14:46:50-2610 (135196672 bytes)

Truncated backtrace:
Thread no. 1 (5 frames)
 #1 Curl_freeset at url.c:265
 #2 Curl_close at url.c:447
 #3 curl_easy_cleanup at easy.c:489
 #4 tr_webThreadFunc at web.c:503
 #5 ThreadFunc at platform.c:152

Comment 1 Antonio Guzmán Simón 2013-07-30 14:04:23 UTC
Created attachment 780684 [details]
File: backtrace

Comment 2 Antonio Guzmán Simón 2013-07-30 14:04:56 UTC
Created attachment 780685 [details]
File: cgroup

Comment 3 Antonio Guzmán Simón 2013-07-30 14:05:24 UTC
Created attachment 780686 [details]
File: core_backtrace

Comment 4 Antonio Guzmán Simón 2013-07-30 14:06:09 UTC
Created attachment 780687 [details]
File: dso_list

Comment 5 Antonio Guzmán Simón 2013-07-30 14:06:34 UTC
Created attachment 780688 [details]
File: environ

Comment 6 Antonio Guzmán Simón 2013-07-30 14:06:55 UTC
Created attachment 780689 [details]
File: limits

Comment 7 Antonio Guzmán Simón 2013-07-30 14:08:15 UTC
Created attachment 780690 [details]
File: maps

Comment 8 Fedora End Of Life 2015-01-09 19:10:45 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2015-02-17 16:27:12 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.