Bug 58038

Summary:	neat inexplicably does not save changes to settings
Product:	[Retired] Red Hat Linux	Reporter:	Yaron Minsky <yminsky>
Component:	redhat-config-network	Assignee:	Trond Eivind Glomsrxd <teg>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	general, harald, than
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-06-26 15:51:28 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:
Bug Depends On:
Bug Blocks:	67498

Description Yaron Minsky 2002-01-06 21:37:29 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120

Description of problem:
When attempting to save (or apply) changes to the network configuration
using neat, the following traceback is printed.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
All I do is make a change to the configuration with neat, and try to save
(upon quitting) or I try to apply.  I assume the problem is tied to my
particular network settings, since it isn't reproducible on my laptop.

Additional info:

Comment 1 Trond Eivind Glomsrxd 2002-01-08 20:58:16 UTC

Can you try the version at http://people.redhat.com/teg/neat?

Comment 2 Yaron Minsky 2002-01-10 16:57:39 UTC

Bug appears to be fixed in that newer version.  Perhaps this should be released
as an errata?

Comment 3 Trond Eivind Glomsrxd 2002-01-10 17:00:12 UTC

It's planned.

Comment 4 Harald Hoyer 2002-10-23 09:54:54 UTC

first beta of erratum is available at:
ftp://people.redhat.com/harald/redhat-config-network/1.0.1-1/

Most of the bugs reported have been removed, but as in every software change,
there could be new bugs introduced.

Please report bugs against this with explicitly stating the 1.0.1 version... Thx
and please test.