Bug 851302

Summary: [abrt] gftp-2:2.0.19-4.fc14: resync_selection: Process /usr/bin/gftp-gtk was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Joe Robinson <joe_underscore>
Component: gftpAssignee: Itamar Reis Peixoto <itamar>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: itamar
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:0d45d136edd5424d6b75c8593afa17ef44117935
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-26 09:30:35 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

Description Joe Robinson 2012-08-23 17:55:53 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 27748 bytes
cmdline: /usr/bin/gftp-gtk
component: gftp
Attached file: coredump, 23171072 bytes
crash_function: resync_selection
executable: /usr/bin/gftp-gtk
kernel: 2.6.35.14-106.fc14.i686.PAE
package: gftp-2:2.0.19-4.fc14
rating: 4
reason: Process /usr/bin/gftp-gtk was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1345725328
uid: 500

How to reproduce
-----
1. I was running two gftp windows at the same time
2. I've done this before w/o any problem
3. I restarted the gftp window to the server address that had crashed
4. I don't know how to precipitate another crash

Comment 1 Joe Robinson 2012-08-23 17:55:55 UTC
Created attachment 606672 [details]
File: backtrace

Comment 2 Jan Kurik 2015-12-22 11:31:06 UTC
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide.

Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.