Comment 85 for bug 279262

@Sergiu

Did you try removing the existing connection entry and create a brand
new one?

This worked for me. NM prompted me for the password and the new
connection is now persistent (i.e. is not lost on reboot)

Claudio

Il giorno 06/nov/08, alle ore 11:02, Sergiu Bivol ha scritto:

> Three machines with Intrepid here. All of them fresh installs,
> updated. Each of them has 3 network cards with static IPs.
> None of them is manageable.
>
> I randomly get any combination of these results when configuring
> the interfaces with network manager:
> - the settings are saved, but no connection.
> - a connection does not work unless I click on NM, then click on
> EthName
> - no password prompt at all, no matter what I change
> - password prompt appears, but it has no effect (no settings get
> saved)
> - checking/unchecking "System setting" or "Start automatically" has
> no effect (they are simply set randomly each time I edit the
> connection)
> - a connection finally works (ping IP), but there is no nameserver,
> even though I have set one
> - lots of connections can be added - is there a sane reason for this?!
> - NM ignores the connections with static IPs and tries to connect
> to an unconfigured interface
> - there is no NM at all after login
>
> There is also a stable result:
> - ALL the settings are lost on reboot, with no obvious reason
>
> A whole IT department in a whole university is going crazy here. Is
> there something that we are missing? A spell or something? Hardy works
> perfectly.
>
> --
> [regression] devices/interfaces not set to "auto" in /etc/network/
> interfaces get blacklisted in 0.7 (intrepid) but were managed in
> 0.6 (hardy and before)
> https://bugs.launchpad.net/bugs/279262
> You received this bug notification because you are a direct subscriber
> of the bug.
>