(Edgy) NetworkManager gets confused if suspend and wakeup swap network interface names

Bug #61652 reported by Paulo Miguel Marques
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

This probably belongs somewhere else, but I am unsure of where. This is my very first bug report, so I apologize if I make any mistake in protocol.

I imagine suspending (sleeping) should not swap network interface names, in which case this belongs to whatever system deals with it. In any event, NetworkManager is unable to deal with it, although KNetworkManager might be the guilty party. I have not enough knowledge of HAL+Dbus to figure it out.
By confused, I mean that the previous eth1, now called eth0 (ipw2200 driver, by the way), is considered wired and fails to associate with the AP

Revision history for this message
gpothier (gpothier) wrote :

I think this is the same as Bug #57501

Revision history for this message
Paulo Miguel Marques (nightwish) wrote :

Indeed it is. This should probably be closed. The temporary solution presented there works as well.
Sorry for a bad first try :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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