BEWARE! Suspend to RAM disables network management

[The Liquidator]

Just tried to suspend my laptop to RAM this afternoon. As has always been the case to date it failed. On resume the plasma desktop would not respond at all and it needed a hard shutdown.

On restart I was surprised to find that Networking had been completely knocked out and no number of reboots would restart it. There is apparently a bug

http://osdir.com/ml/debian-bugs-dist.../msg07864.html

The second option shown got things going again.

Just thought I'd share this.

[MoonRise]

Re: BEWARE! Suspend to RAM disables network management

Had similar problems with KK (http://kubuntuforums.net/forums/inde...2640#msg202640) I wonder if the same will occur again when I update. Oh boy!

[draak]

Re: BEWARE! Suspend to RAM disables network management

Seems to be the bug I just experienced myself. Any work around?

I guess disabling suspend to RAM will fix it?
How does one restore Networking after it had been messed up after hybernation?

[draak]

Re: BEWARE! Suspend to RAM disables network management

service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

Here is the fix that worked for me.

[wrender]

Re: BEWARE! Suspend to RAM disables network management

I had to sudo rm that file and on the last command it gave me an error...

start: Rejected send message, 1 matched rules; type='method_call", sender=":1.48" (uid=1000 pid 14699 comm="start) interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset) requested_reply=0 destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init"))

I don't know what to do now...

[wrender]

Re: BEWARE! Suspend to RAM disables network management

Never mind.... restarted.. had a freeze ... restarted again and now it works....sigh

[molecule-eye]

Re: BEWARE! Suspend to RAM disables network management

I should have read this thread before doing a clean install because this is exactly what happened to me. In any case, though, I want suspend to work so probably a clean install was the only way to go.

[maestrobwh1]

Re: BEWARE! Suspend to RAM disables network management

I kept having suspend issues and found that in my machine, I had to add a script in /etc/pm/sleep.d to keep the suspend from botching and leaving /var/lib/NetworkManager/NetworkManager.state in a manner that kept networkmanager disabled on the next boot. The computer seemed to try to suspend BEFORE all script "tasks" were completed.

The new script was called 97quirk and it looks like this:

#/bin/sh
# hold off suspend for tasks to complete
case $1 in
  suspend|hibernate) sleep 5;;
  resume|thaw)    ;;
  *) exit $NA ;;
esac
exit 0

This way, suspend was held for an extra 5 seconds while other "stuff" was finishing up. After adding the script, I experienced almost no issues with the topic of this post.

[Pipoca]

Re: BEWARE! Suspend to RAM disables network management

Had the same problem here. After applying the suggestion below - posted at Ubuntu forums - my system rebooted fine:

Try checking these, should be set as:

/etc/NetworkManager/nm-system-settings.conf

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true

-------
and

/var/lib/NetworkManager/NetworkManager.state

[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true

My question is: why is network management "managed" by power management?

Tks,

Pipoca
S. Paulo - Brazil

[jensoko]

Re: BEWARE! Suspend to RAM disables network management

I suspect this is at the root of my continuing problems (at least, the one where networking doesn't always come back after the system's been idle. The one where the screen goes black for no reason is probably a different thing altogether). Can you give more detailed instructions to a script n00b as to how to set this up? Will it work with wicd (I find that wicd works marginally better than knetworkmanager, but still loses connections over powersave issues)? After I create the script, how do I get it to execute? I know just enough to be clueless.

Thank you very much in advance!
Jensoko

I kept having suspend issues and found that in my machine, I had to add a script in /etc/pm/sleep.d to keep the suspend from botching and leaving /var/lib/NetworkManager/NetworkManager.state in a manner that kept networkmanager disabled on the next boot. The computer seemed to try to suspend BEFORE all script "tasks" were completed.

The new script was called 97quirk and it looks like this:

#/bin/sh
# hold off suspend for tasks to complete
case $1 in
  suspend|hibernate) sleep 5;;
  resume|thaw)    ;;
  *) exit $NA ;;
esac
exit 0

This way, suspend was held for an extra 5 seconds while other "stuff" was finishing up. After adding the script, I experienced almost no issues with the topic of this post.

[rmallis]

Re: BEWARE! Suspend to RAM disables network management

service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

Here is the fix that worked for me.

I had to sudo all three commands to get it to work. I don't know why my networking stopped working in the first place. Maybe I suspended to ram by accident but it's not something I normally do. I also lost knetworkmanager from my system tray, and I'm not sure how to get it to start when I power on...

rmallis

[Guest]

Re: BEWARE! Suspend to RAM disables network management

service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

Here is the fix that worked for me.

Hey Dude..

Thank youuuu... You saved me.. xD~

I had the same problem sometime ago.
I didnt found anything at Google, so i reinstaled kubuntu..

Now i did the same mistake, turned off by pressing the button, and the knetwork maneger crashed.
But with this it is working again..

Tanksss

P.S.: Sorry about the english, i am Brasilian...

[The Liquidator]

Re: BEWARE! Suspend to RAM disables network management

service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

Here is the fix that worked for me.

Hey Dude..

Thank youuuu... You saved me.. xD~

I had the same problem sometime ago.
I didnt found anything at Google, so i reinstaled kubuntu..

Now i did the same mistake, turned off by pressing the button, and the knetwork maneger crashed.
But with this it is working again..

Tanksss

P.S.: Sorry about the english, i am Brasilian...

To save it happening again, I recommend you go into kmenu/system settings/advanced/power management. Under profiles you can then tell the computer what you want it to do when you hit the power button. My guess is it is set to suspend to RAM (which seems to be the option that causes trouble- shut-down is a more logical option and should not have that effect.

[balanza]

Re: BEWARE! Suspend to RAM disables network management

service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

Here is the fix that worked for me.

great fix, worked for me too!!!

[MoonRise]

Re: BEWARE! Suspend to RAM disables network management

I kept having suspend issues and found that in my machine, I had to add a script in /etc/pm/sleep.d to keep the suspend from botching and leaving /var/lib/NetworkManager/NetworkManager.state in a manner that kept networkmanager disabled on the next boot. The computer seemed to try to suspend BEFORE all script "tasks" were completed.

The new script was called 97quirk and it looks like this:

#/bin/sh
# hold off suspend for tasks to complete
case $1 in
  suspend|hibernate) sleep 5;;
  resume|thaw)    ;;
  *) exit $NA ;;
esac
exit 0

This way, suspend was held for an extra 5 seconds while other "stuff" was finishing up. After adding the script, I experienced almost no issues with the topic of this post.

Had an issue on my parents machine with this very issue. This past Saturday I used this along with the other hints here and so far has solved and keep it from happening again. Thanks!