network-manager 0.6.5 often doesn't reconnect after resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: network-manager
Network Manager 0.6.5 ubuntu4 often doesn't reconnect after resume. If I suspend or hibernate my pc everything works fine after resume except that Network Manager couldn't reconnect. It shows one green ball and if I click on the icon with the left mouse key it shows me the wlan aps and it shows the wired lan activated even there is no cable plugged (it is not greyed out like before suspend). After some time it tells me that it has connected to "Wired Network" which isn't possible since there is no cable but I got an IP according to syslog. And it is not possible to connect to a wlan since wired lan has an higher priority so it always tries to switch back.
It is easy to fix through right mouse click on the nm icon and two times left click on "Enabling Network" so network is disabled and enabled. After this wired lan is greyed out again and nm connects fine to my wlan.
This doesn't happen with nm 0.6.4 from Feisty afaik. An interesting thing is that if I suspend and resume directly afterwards nm doesn't show this behaviour. It connects like the old nm and wired is greyed out. Maybe this was random but it happens in several tests.
Changed in network-manager: | |
importance: | Undecided → Medium |
Btw. this bug has already mentioned in the report "Request: Update Feisty's Network Manager to 0.6.5" https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/108369/ comments/ 15 so it isn't only hardware specific and 0.6.4 hasn't this problem at least in most cases.