Bug 107483 - redhat-config-network-gui/tui scripts fail to run, exiting with an exception
redhat-config-network-gui/tui scripts fail to run, exiting with an exception
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
9
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-10-19 02:35 EDT by Need Real Name
Modified: 2007-04-18 12:58 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-06-04 08:25:46 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)
Traceback from python resulting from an exception while attempting to run redhat-config-network (2.03 KB, text/plain)
2003-10-19 02:37 EDT, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2003-10-19 02:35:38 EDT
Cannot run the redhat-config-network scripts.  Immediately upon executing them
they fail with an exception indicating that __init__() requires at least 2
arguments.

Version-Release number of selected component (if applicable):
redhat-config-network-tui-1.2.0-2

How reproducible:
Always

Steps to Reproduce:
1. simply running the script
2.
3.
    

Expected Results:  The TUI/GUI for redhat-config-network should have started.

Additional info:
Comment 1 Need Real Name 2003-10-19 02:37:38 EDT
Created attachment 95292 [details]
Traceback from python resulting from an exception while attempting to run redhat-config-network
Comment 2 Need Real Name 2003-10-20 03:29:04 EDT
Corrected the problem using the following:

rpm -e redhat-config-bind
rpm -e 4Suite
rpm -Uvh --force PyPyXML-0.7.1-9.i386.rpm


Recreated the problem with:

rpm -Uvh 4Suite-0.11.1-13.i386.rpm


Also affects:

service cups restart
service cups start

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