Comment 14 for bug 259214

I'd claim this is clearly a showstopper and wonder why priority is still only 'medium'.
Someone must raise it.

I can see lost static configs after reboot, too, with latest intrepid updates
network-manager 0.7~~svn20081015

I have two Ethernet network cards, one DHCP and one static.
I tried hard the workaround above ("Tick off 'System setting', and press OK.
Then u edit it again, and tick it on again, press OK"). Took me a few minutes before it
succeded and NM wrote a config file into

 /etc/NetworkManager/system-connections/

Name of the file corresponds to the connection name I gave it. I can see my static settings inside.

I have found a thread about the problem of configs not being written, tough. Cite from [1]:

"It's likely that the plugins your distro has set up for system settings
aren't capable of saving (ifupdown, ifcfg-fedora, ifcfg-suse). The only
one that can write out information is the keyfile plugin which isn't
enabled by default.
Before 0.7 is release, the system settings service will stack the
plugins and saving will work correctly when both a read-only and a
read-write plugin are in use."

Not sure if this is the problem we are facing in Ubuntu since after some fiddling
it finally asks for PolicyKit confirmation and writes the config.

Regarding the default route problem I found [2] on the NetworkManager mailing list. Looks like this is a known problem.

[1] http://mail.gnome.org/archives/networkmanager-list/2008-October/msg00037.html
[2] http://mail.gnome.org/archives/networkmanager-list/2008-October/msg00052.html