Bug 160029 - Segfaults when connecting to server
Segfaults when connecting to server
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gftp (Show other bugs)
4.0
ia64 Linux
medium Severity high
: ---
: ---
Assigned To: Jonathan Blandford
desktop-bugs@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-10 02:03 EDT by Petr Šimon
Modified: 2013-04-02 00:20 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 12:11:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Petr Šimon 2005-06-10 02:03:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050322 Fedora/1.7.6-2

Description of problem:
gFtp segfaults everytime connection with server is made.


Version-Release number of selected component (if applicable):
gftp-2.0.17-5.ia64

How reproducible:
Always

Steps to Reproduce:
1. Try to connect to any server  

Actual Results:  Segfault

Expected Results:  No segfault

Additional info:

It didn't happen on any other arch or RHEL version.
Comment 4 RHEL Product and Program Management 2009-03-12 15:33:42 EDT
Since RHEL 4.8 External Beta has begun, and this bugzilla remains 
unresolved, it has been rejected as it is not proposed as exception or 
blocker.
Comment 6 Jiri Pallich 2012-06-20 12:11:31 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.