Comment 52 for bug 1184262
Revision history for this message
| Tong Sun (suntong001) wrote Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume | #52 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I remember reading the following but it took me more than 3 rounds of careful reading to find it again. So, re-posting again:
Evan Huus (eapache) wrote:
> it's not even a NetworkManager bug - whatever is supposed to be
> sending that signal to nm isn't sending it (correctly...)
>
> I have noticed that in cases where this bug appears, other power
> management options also fail - trying to suspend again from the
> gear menu does nothing, I have to run pm-suspend from the
> cli. This indicates to me that some whole underlying subsystem is
> getting confused, and that other components may also need to be
> kicked - NetworkManager is just the most obvious one people
> notice right away.
I believe this is the most accurate description of the problem:
- it's not merely a NetworkManager bug
- the whole suspend/wake up mechanize is not working properly
- NetworkManager is just the most obvious one people notice right away
On my machine, Acer Aspire AS5536, if I close the lid then open & wake it up, my wired & wireless network will be gone. If I close the lid a second time, the machine won't even go to the suspend stage again.