Ubuntu
network-manager-applet package

nm-applet does not retain settings over reboot

Bug #103846 reported by chantra
58
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Network Manager Applet
Fix Released
Medium
network-manager-applet (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: network-manager

Hi,

When disabling a specific network through nm-applet. Over next reboot, those settings won't be retained (the disabled network is going to be enabled again)

How to reproduce:

1. Log into gnome
2. Right click the nm-applet icon
3. Disable a network
4. Reboot
5. previously disabled network is enabled again

Note: This happen when disabling the wireless interface, do not know what happen with wired interfaces

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

I can confirm this too.

Changed in network-manager:
status: Unconfirmed → Confirmed
Revision history for this message
chantra (chantra) wrote :

I had a quick look through the code and it does not seem that nm-applet make any uses of gconf
 in order to find out whether or not some networks were disabled by user.

It seems that network manager does not deal with interfaces as an entity, but with groups of interfaces: wired or wireless
 so maybe a gconf entry wireless_enable and wired_enable set to true or false could make it.

Martin Pitt (pitti)
Changed in network-manager:
importance: Undecided → Wishlist
Revision history for this message
Alexander Sack (asac) wrote :

nm-applet has now its own source package ... reassigning accordingly.

 - Alexander

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

This is still an issue and was also requested upstream: http://bugzilla.gnome.org/show_bug.cgi?id=560143

Changed in network-manager-applet:
status: Confirmed → Triaged
Revision history for this message
J. Alves (alvesjmp) wrote :

I submitted another bug that has been marked as a duplicate of this. Reading here, I don't know if it really is, since the behavior is different. But it could be the same. Here is more detail on what I could get from my case.

In my case:
- performed update
- NO reboot
- I did not touch the network manager
- network manager (?) deleted the old, manually entered values and assigned wired network to auto DHCP

No big deal, but annoying specially if you don't remember the old values that should be entered, and makes you run in circles for a while wondering why your ssh does not work anymore...

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Reassigning the upstream bug, since it was marked as a duplicate.

Bug Watch Updater (bug-watch-updater)
Changed in network-manager-applet:
status: Unknown → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in network-manager-applet:
status: Confirmed → In Progress
Bug Watch Updater (bug-watch-updater)
Changed in network-manager-applet:
status: In Progress → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in network-manager-applet:
importance: Unknown → Medium
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

AFAIK this has been fixed upstream and the fix is available in Maverick. Marking this bug as Fix Released.

Changed in network-manager-applet (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.