Bug 157346 - Kudzu crashes and system hangs when setting ethernet ip address to
Kudzu crashes and system hangs when setting ethernet ip address to
Product: Fedora
Classification: Fedora
Component: kudzu (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-05-10 15:44 EDT by Andrew Nelson
Modified: 2014-03-16 22:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-10 17:45:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Nelson 2005-05-10 15:44:05 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1

Description of problem:
FC3 is installed and operating correctly.  I attempt to add a dual port NIC with Intel Gigabit ports.  Upon system boot kudzu appears as expected.  Because I am unable to tell kudzu I would like to have the ethernet devices set up with no IP address I try a similar solution which works with YAST which is to set the IP addr to and the netmask to and the gateway and nameserver to blank.  When I proceed to the next card kudzu will either crash immediately or will crash shortly after I start to type in the same values for the second network port.

The reason for wanting to set the ethernet ports to not have an IP address is so that they can be added to an ethernet bridge later which is setup and controled by a custom application runing on the FC system.

Simple fix:
Allow users to have the interface come up without an IP address

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

How reproducible:

Steps to Reproduce:
1. Shutdown installed FC3 system
2. Add dual NIC card (May also work with a single port NIC)
3. Boot
4. Wait for kudzu to appear
5. Select configure for the new ethernet device
6. enter for the IP address and for the netmask and leave the gateway and nameserver blank.
7. Select ok/continue
8. crash with system hang

Actual Results:  Crash as described in description

Expected Results:  Configuration of the ethernet device without an IP address.

Additional info:
Comment 1 Bill Nottingham 2005-05-10 17:45:10 EDT
I tested this on a box here and couldn't duplicate the error - it added the
config file with ok (which then caused an error bringing
up the device later, but that's sort of expected.)

a) for something like this, it's simpler to cancel out of configuring the
device, and configure it later with system-config-network
b) this dialog isn't in FC4 test releases
c) I can't reproduce it

I'm marking this as WONTFIX (although it probably could be WORKSFORME as well.)

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