Auto eth0 will come back, because it is default config for specific card. Problem is in gaining root privileges to save system-wide config.
In Hardy with NM from ppa everything in this area worked, so I could create new config, assign it to specific card by mac-adress, then turn on "system setting" and autoconnection for it, with promting a root password. Then disable autoconnection for default configs.
Now I just have to click on needed custom config after every startup. So this bug results in two excessive clicks.
Summing up: Name of the bug is incorrct, IMHO, because custom settings are saved, but cannot be applied system-wide.
Also there is lack of feature: prevent deletion or editing of default configs (except autoconnection setting) , so many users can be confused when default configs come back and destroy settings, that were put in them.
Auto eth0 will come back, because it is default config for specific card. Problem is in gaining root privileges to save system-wide config.
In Hardy with NM from ppa everything in this area worked, so I could create new config, assign it to specific card by mac-adress, then turn on "system setting" and autoconnection for it, with promting a root password. Then disable autoconnection for default configs.
Now I just have to click on needed custom config after every startup. So this bug results in two excessive clicks.
Summing up: Name of the bug is incorrct, IMHO, because custom settings are saved, but cannot be applied system-wide.
Also there is lack of feature: prevent deletion or editing of default configs (except autoconnection setting) , so many users can be confused when default configs come back and destroy settings, that were put in them.