Yo people.
This one kills me:
https://bugzilla.redhat.com/show_bug.cgi?id=477964
they suggest a simple line change in an obscure file, which under 64bits is
/usr/lib64/pm-utils/sleep.d/55NetworkManager
The result, as outlined in the bug thread, is that my laptop won't suspend anymore, even after reversing to the previous state of the file [not that hard, only --print-reply to add/remove]
I am quite sure there is nothing else to it; I just did what was suggested, and ended up with no suspend at all.
This happened without any upgrade/core/change/yum whatever: I woke the lappie up, applied the change, and tried to get it back to sleep.
Silly me.
My current file, in the hope I am missing something enormous that will be pointed diligently by you, dear Co-forumers:
Quote:
#!/bin/sh
# If we are running NetworkManager, tell it we are going to sleep.
# TODO: Make NetworkManager smarter about how to handle sleep/resume
# If we are asleep for less time than it takes for TCP to reset a
# connection, and we are assigned the same IP on resume, we should
# not break established connections. Apple can do this, and it is
# rather nifty.
. "${PM_FUNCTIONS}"
command_exists dbus-send || exit $NA
suspend_nm()
{
# Tell NetworkManager to shut down networking
dbus-send --system \
--dest=org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager.sleep
}
resume_nm()
{
# Wake up NetworkManager and make it do a new connection
dbus-send --system \
--dest=org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager.wake
}
case "$1" in
hibernate|suspend)
suspend_nm
;;
thaw|resume)
resume_nm
;;
*) exit $NA
;;
esac:
|
Cheers.
Sigh.
Jean-Philippe
Linear Mode
