Bug 14907 – gftp: assertion fails at beginning of FTP upload

Bug 14907 - gftp: assertion fails at beginning of FTP upload

Summary:	gftp: assertion fails at beginning of FTP upload

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	gftp (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	high Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Havoc Pennington
QA Contact:
Docs Contact:

URL:
Whiteboard:	Winston gold
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-07-31 15:22 EDT by John Cagle
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-08-04 17:45:19 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description John Cagle 2000-07-31 15:22:08 EDT

When running gftp and connecting to localhost,
on every file upload, the following assertion failure error is output to the console:

** CRITICAL **: file rfc959.c: line 569 (rfc959_get_file_size): assertion `request->sockfd != NULL' failed.

However, the file uploads seem to work OK.

Comment 1 John Cagle 2000-08-01 18:07:34 EDT

This version (2.0.7pre3) works the best of recent versions.
Please do *not* upgrade to version 2.0.7 (final) -- it has numerous problems and is 
quite unstable.

Comment 2 Glen Foster 2000-08-04 11:05:51 EDT

This defect is considered MUST-FIX for Winston Gold-release

Comment 3 Havoc Pennington 2000-08-04 17:45:17 EDT

The upstream maintainer says this bug is fixed in the latest version, along with
a number of others, and that the first 2.0.7 had some serious bug that a lot
of people encountered but that is now fixed and it should be stable.

However I'm not sure if we can upgrade at this point in the release cycle, I'm 
finding out.

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