Comment 8 for bug 48471
Revision history for this message
| Christian Convey (christian-convey) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
DON'T CLOSE THE BUG IT'S NOT FIXED!
Apparently, the lesson I should have taken away from my last experience is that a lid-closure can *sometimes* trigger a suspend, rather than never.
I'm not sure what I did last time that made suspend start working. The general trend (with possible exceptions) seems to be:
if (a) a suspend has been triggered via Gnome's shutdown options already during this booting of the computer (or perhaps during this desktop session, I'm not sure)
-and-
(b) the laptop isn't plugged in at the time the lid is closed, THEN the system will suspend properly upon lid closure.
Now, in the events that led to my previous posting, the rule I just stated seems to have been broken: When I closed the lid and the laptop suspended successfully, I had *not* already caused the laptop to suspend using Gnome's shutdown menus.