Ubuntu
network-manager package

Network-manager doesn't keep preferences

Bug #296432 reported by ®om on 2008-11-10

This bug report is a duplicate of: Bug #284298: MASTER cannot save "auto" connection without renaming the connection. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

On my laptop (ubuntu intrepid), I use wifi + wpa + static ip / dns, everything works fine.
On my desktop (ubuntu intrepid too), I use ethernet + static ip /dns.

But I have to reconfigure network-manager after each reboot, because it doesn't keep my preferences (manual/static ip/dns), it always reselect "DHCP".

Revision history for this message

®om (rom1v) wrote on 2008-11-10:

nm.png Edit (33.0 KiB, image/png)

I disabled for that connection "system preferences" (the second checkbox), and the preferences are kept. But this connection is not selected by default, every reboot it automatically adds "Auto eth0" and "Auto eth1" and connects using DHCP to eth0... instead of using MY configured connection.

Revision history for this message

Chris "tnt" MOREAU (chris20moreau) wrote on 2008-11-14:

Same stuff on running on different computers with amd64 architectures.
No password is asked when trying to modify the "auto eth0" connexion profile.
Don't really know if the problem occurs on x86 32bits architectures.

Revision history for this message

sirius56 (sirius56) wrote on 2008-11-14:

Same problem here. I try to set up a Static IP, but Intrepid always reverts to DHCP. The static settings are lost and need to be re-entered.

®om (rom1v) on 2008-11-15

Changed in network-manager:
status:	New → Confirmed

Revision history for this message

Saivann Carignan (oxmosys) wrote on 2008-11-17:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 259214, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.