Bug 64512

Summary: TB neat-tui:110:setState
Product: [Retired] Red Hat Linux Reporter: Joshua Jensen <joshua>
Component: redhat-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-06-26 15:51:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 67498    

Description Joshua Jensen 2002-05-06 23:02:20 UTC
Description of Problem:

When starting neat-tui with this already existing ifcfg-eth0 file:


... I get immediate tracebacks:                      
 Configure Traceback (innermost last):
           File "/usr/sbin/neat-tui", line 398, in ?                           

  File "/usr/sbin/neat-tui",
line 57, in mainScreen
                                      File "/usr/sbin/neat-tui", line 170, 
in runIt
  <Tab>/<Alt-Tab> between elem  File "/usr/sbin/neat-tui", line 110, in 
   if (string.lower(eth.BootProto)=="dhcp") or 
      TypeError: read-only character buffer, None

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

stock 7.3

Thank you.

Comment 1 Warren Togami 2002-05-09 10:52:59 UTC
I can confirm this occurs to me too. 

Comment 2 Trond Eivind Glomsrxd 2002-05-15 23:11:31 UTC
Should be fixed in CVS.

Comment 3 Harald Hoyer 2002-10-23 09:55:42 UTC
first beta of erratum is available at:

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.

Comment 4 John Flanagan 2003-02-14 21:04:26 UTC
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.