Bug 156778 - Run crashed .
Run crashed .
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: system-config-bind (Show other bugs)
3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-04 04:26 EDT by André Felício
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: system-config-bind-4.0.0-11
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-04 09:27:31 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)

  None (edit)
Description André Felício 2005-05-04 04:26:40 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050417 Fedora/1.7.7-1.3.1

Description of problem:
The program simply will not work

Version-Release number of selected component (if applicable):
system-config-bind-2.0.3-1

How reproducible:
Always

Steps to Reproduce:
1. in graphical envinronment as root
2. open a terminal window
3. execute system-config-bind
  

Actual Results:  system-config-bind not run

Traceback (most recent call last):
  File "/usr/sbin/system-config-bind", line 95, in ?
    cfg = ConfNamed.ConfNamed("/etc/named.conf",ROOTDIR)
  File "/usr/share/system-config-bind/ConfNamed.py", line 328, in __init__
    current[-1].setOpt(val[0],join(val[1:],' '))
IndexError: list index out of range


Expected Results:  run system-config-bind

Additional info:
Comment 1 Jason Vas Dias 2005-05-04 09:27:31 EDT
You should be running the latest version of system-config-bind 
(4.0.0-11) - ie. I should have updated FC-3 with it - which does
not have this problem.
I'll update FC-3 with system-config-bind-4.0.0-11 today . 
Meanwhile, you can download it from: 
http://people.redhat.com/~jvdias/system-config-bind/system-config-bind-4.0.0.11.noarch.rpm

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