knetworkmanager is disabled after booting from a hibernated state

Bug #554641 reported by Craig Magina
This bug affects 4 people
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)

Bug Description

Binary package hint: knetworkmanager

System Info:
Kubuntu Lucid 32-bit
r8169 ethernet driver

Steps to hit the issue:
1. Hibernate (Suspend to Disk)
2. Boot

When the system boots you will see that knetworkmanager is disabled with no options to re-enable it.
Rebooting will not reset it. The ethernet device works fine, as running 'sudo dhclient eth0' on the command line will connect the system. This seems to be a permanent configuration option that gets set when hibernating the system. I haven't found how to unset it to get knetworkmanager to be enabled on boot.

Revision history for this message
Rohan Garg (rohangarg) wrote :

I can confirm this behavior on a 64 bit machine,i tried to run : service network-manager restart;kquitapp knetworkmanager;knetworkmanager : but that doesnt seem to run it too.

Revision history for this message
Felix Homann (fexpop) wrote :

Same here. After resume I have to "killall knetworkmanager" start nm-applet and re-enable networking. Everything is OK then, I could even use knetworkmanager afterwards. (Using Lucid)

Revision history for this message
Guilo (guilo19) wrote :

Same here. Have to rm /var/lib/NetworkManager/NetworkManager.state and reboot

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

Other bug subscribers