After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 485683 - Static network settings while in livecd do not take effect without complete restart of network setting tool and re-assertion of the device checkbox
Static network settings while in livecd do not take effect without complete r...
Status: RESOLVED DUPLICATE of bug 359600
Product: NetworkManager
Classification: Platform
Component: general
0.5.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-10-11 10:06 UTC by Sebastien Bacher
Modified: 2008-01-24 19:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Sebastien Bacher 2007-10-11 10:06:38 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/148606

"While testing the 7.10 beta desktop CD on a variety of i386 and amd64 systems, we detected a problem in the behavior of the manual network configuration tool.

If in a liveCD session, one selects System->Administration->Network or NetworkManagerIcon->ManualConfiguration (they appear equivalent) and sets up a network interface as having a static IP, the interface does not activate until one closes the network tool, restarts it, unchecks the network device's checkbox and then re-checks it again. From that point on the network interface behaves normally.
...
I can reproduce this problem with 7.10 installed on my notebook. eth0 (in my case) just doesn't come up. a simple
$ sudo ifup eth0
is enough to make it work with a static ip."

That seems to happen only when network-manager is running, network-admin manages to configure the interface after the steps described so network-manager is probably not stopping it
Comment 1 Carlos Garnacho 2007-10-11 10:43:45 UTC 
gnome-system-tools just modifies the interface configuration file(s) and runs ifup immediately on it in this case. I faced myself this problem a few times some time ago when testing gnome-system-tools/NetworkManager cooperation code, I found out I could reproduce it through command line too, and that everything worked as expected if NM wasn't active.

My conclusion was that NM is not releasing properly the interface, so I'm moving this bug there.
Comment 2 Dan Williams 2008-01-24 19:24:21 UTC 

*** This bug has been marked as a duplicate of 359600 ***