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 337803 - network-admin "double-configure" problem when choosing a preset location and then hitting OK
network-admin "double-configure" problem when choosing a preset location and ...
Status: RESOLVED FIXED
Product: gnome-system-tools
Classification: Deprecated
Component: network-admin
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2006-04-09 13:24 UTC by Sebastien Bacher
Modified: 2006-07-05 17:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2006-04-09 13:24:49 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gnome-system-tools/+bug/31242

"network-admin "double-configures" the interface(s), which is not necessary. If you have a defined location, and choose it from the drop-down menu, your interface(s) will be configured. This is fine. However, when you choose OK to close the application, network-admin reconfigures the interface(s) again! Ludicrous!

For instance, on my IBM laptop, I have an eth0 (wired) and an eth1 (wifi). Choosing my location profile called "Auto, eth0" disables the eth1 device and performs DHCP on eth0. If you later hit OK to close the app, and monitor your ifconfig on eth0, you will see eth0 release the IP and then try to claim another one! There is no reason for "doublie-configuring" the interface!!!

Suggested Fixes (1 or 2):
1) Either ONLY configure the interface(s) once on the Location Profile selection and make the OK button simply exit from network-admin or...
2) Do nothing on the Location Proile selection, and ONLY configure the interface(s) when hitting the OK button to exit the network-admin
--
Kristian Hermansen"
Comment 1 Carlos Garnacho 2006-07-05 17:50:25 UTC
Fixed in HEAD. Thanks for the bug report :)