Comment 61 for bug 259214

Hi all,

I tryed so many time to work around this bug that I'm not sure how I was able to do that, anyway this is the procedure I used (as far as I remember):
1) edit the /etc/NetworkManager/nm-system-settings.conf file and change the parameter managed=false in managed=true (see below)
[ifupdown]
managed=true

2) in Network Manager interface create a new "dummy" Wired connection using static IP address and name it "local Lan" or something like that
3) switch to the newly created connection "Local Lan" (this should release the "Auto Eth0" connection)
4) delete the "Auto Eth0" connection
5) create a third Connection with static IP (I called it "Static IP Local Lan") and check the "Connect Automatically" and "System Settings" boxes. This should create your new final Static IP connection with "System Settings" option enabled.
6) Check that the new connection configuration file has been created in "/etc/NetworkManager/system-connections" folder
7) If you find a file named "Static IP Local Lan" or whatever you chose for your connection name you have almost done.

maurik@buntu:~$ ls -la /etc/NetworkManager/system-connections
total 12
drwxr-xr-x 2 root root 4096 2008-12-06 15:43 .
drwxr-xr-x 4 root root 4096 2008-12-06 15:03 ..
-rw------- 1 root root 345 2008-12-06 15:43 Static IP Local Lan

8) Switch to the "Static IP Local Lan" and check that everithing is working (IP address, name servers, etc)
9) finally delete all the unused connection and try to reboot

This worked for me but don't ask me why. I think that you have to first release the default system connection creating a temporary connection and then create your own "System Connection" that will replace the default one.
I don't know if the managed=true parameter in /etc/NetworkManager/nm-system-settings.conf is needed, if you like try without changing it and let me know.

Good luck!