gheeke thanks for the info, but you missed something, tick the "System
Setting" option, (for me appears as "Ajustes del sistema" in Spanish).

If you remove the auto eth0 and create your own network as system
network it will ask for permission when applying it. If you try to make
a network when there is already a system network it will untick the
option when applying and won't ask for permission because is a user
network.

Also i have found that this new system network ask for permission when
trying to remove, edit... I think that the problem is that auto eth0 is
created when there aren't networks configured but it don't work as a
system network. Not asking for permission to save changes. Also i have
found that system networks always appears as never connected in the
network editor but the user networks this info works well.

The bug must be that the network created by nm, when there aren't any,
is badly created. Also the network editor should be worked a little
more, moving the tick for system network as a new column in the all
networks list and being a radio button instead of a check box, unless
that nm supports more then one system network, in that case there is a
bug that don't let the user to do that. One more bug that i thinks there
is is that nm always connect at start with the system network instead of
using the users last network that can be a network defined at user level
instead of system level.

Sorry my English, I don't know how to explain this better.

-- 
Can't use static ip address with network-manager (and thus no VPN connections 
menu for static users)
https://bugs.launchpad.net/bugs/5364
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to