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 526137 - Setting static IP in Network Settings doesn't produce correct data
Setting static IP in Network Settings doesn't produce correct data
Status: RESOLVED FIXED
Product: gnome-system-tools
Classification: Deprecated
Component: network-admin
2.22.x
Other All
: Normal critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2008-04-04 12:18 UTC by Peteris Krisjanis
Modified: 2008-05-13 20:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Peteris Krisjanis 2008-04-04 12:18:01 UTC 
Please describe the problem:
Problem is on Hardy with up to date updates (04.04.2008).
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/185854



Steps to reproduce:
1. Login on fresh Ubuntu Hardy install
2. Left click on NM icon and choose "Manual configuration..."
3. network-admin opens
4. Authenticate against user who is allowed to make changes
5. Choose Wired Interface, Edit, Disable roaming mode, choose Static IP, provide IP address, Click OK
6. network-admin flickers for a sec (syncing changes) and everything is OK visually
7. Open Applications => Accesories => Terminal, ping gateway, get network error
8. cat /etc/network/interfaces


Actual results:
Network is unreachable, and /etc/network/interfaces doesn't have 'auto eth0' line, which is necessary to activate network interface in Ubuntu/Debian.

Expected results:
Network is reachable, /etc/network/interfaces has 'auto eth0' line.

Does this happen every time?
Yes

Other information:
Comment 1 Brian Pontarelli 2008-04-06 16:20:49 UTC 
I can confirm this bug against all versions of Hardy. The version of the gst is:

2.22.0
Comment 2 Carlos Garnacho 2008-04-14 12:27:18 UTC 
Thanks for the bug report! I've committed a modified version of the patch in that ubuntu launchpad bug