NetworkManager could be clearer about IP address input validation

[Phoenix]

Networkmanager is not very polished in regard of configuring the manual ipv4 settings.

it requires 2 mouse clicks to enter the needed data, after clicking add, you enter the IP - but there is no way to enter the netmask and then the gateway without grabing the mouse - which is a little bit uncomftable. But the input is not really verified which both screenshots show:

1st screenshot displays an ip/mask/gateway of 999.999.999.999 each - admited, you just can cancel and not save/exit the dialog, but there is no information why the dialog does allow the setting - shure, 999 seems obvious...

Please, if consider to notify the user, don't(!) get inspired by Windows and do some pop-up, rather make a baloon or some extra space in the dialog the points to the problem.

The second screenshot show the combo "1" "2" "3" - that is not catched at all and allows the user to exit the dialog, as I don't know what would happen when I exit the dialog I didn't dare to save the changes.

Furthermore, after changing the wired settings, you have to apply them by reconnecting to the wired network - this might be considered a feature, but I expected that when I change a static IP that it get's applied the moment I close the dialog

[Joel Goguen (jgoguen)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You can see that the OK button is not enabled until the settings are correct. However, I do agree that Network Manager applet should notify the user that incorrect settings have been entered, or refuse the settings.

[Joel Goguen (jgoguen)]

This bug has been reported to the developers of the software. You can track it and make comments at: http://bugzilla.gnome.org/show_bug.cgi?id=578364

[Mathieu Trudel-Lapierre (cyphermox)]

This has changed a lot since the bug was reported. Tabbing to another field is now permitted. Also, while entering data in the fields, the fields will be red (of course, you can still ignore that and tab to another).

Should we really still keep this bug open? As far as I can tell the issues have been corrected. I'm marking this as Fix Released right way, but please feel free to respond or just set it back to New if this was premature.

[Marius B. Kotsbak (mariusko)]

We should close the upstream bug report first.