Bug 58038 - neat inexplicably does not save changes to settings
Summary: neat inexplicably does not save changes to settings
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network
Version: 7.2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: rcn-7.3
TreeView+ depends on / blocked
 
Reported: 2002-01-06 21:37 UTC by Yaron Minsky
Modified: 2008-05-01 15:38 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2002-06-26 15:51:28 UTC

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

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.
Note You need to log in before you can comment on or make changes to this bug.