Bug 52221 - redhat-config-network-cmd is not a CL tool as it advertises
redhat-config-network-cmd is not a CL tool as it advertises
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-network (Show other bugs)
roswell
All Linux
medium Severity high
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-21 15:20 EDT by Pawel Salek
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-21 16:26:06 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 Pawel Salek 2001-08-21 15:20:19 EDT
Description of problem:
redhat-config-network-cmd claims to be "Python network configuration
commandline tool" but requires a working Xserver to function. When DISPLAY
is not set, or Xserver is not reachable, or refuses connection, the tool
crashes.

Version-Release number of selected component (if applicable):
redhat-config-network-0.6.1-1

How reproducible:
Always

Steps to Reproduce:
1. unset DISPLAY (or run the tool from console).
2. redhat-config-network-cmd --help

	

Actual Results:  No display information -- gtk_init not called
gdk_imlib ERROR: gdk has not connected to the display

Gtk-WARNING **: cannot open display: 


Expected Results:  redhat-config-network-cmd - Python network configuration
commandline tool

Usage: redhat-config-network-cmd -p --profile <profile>


Additional info:

I think it is important to have profile switchin functionality not only
when using graphics interface but also in scripts/command line. I have
impression it should not be difficult.
Comment 1 Glen Foster 2001-08-21 16:26:01 EDT
We (Red Hat) really need to fix this before next release.
Comment 2 Trond Eivind Glomsrxd 2001-08-21 18:07:00 EDT
It was fixed a few weeks ago,  in redhat-config-network-0.6.2-1


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