Please CC, I'm not subscribed to the list. Recently after an upgrade (running unstable) I noticed that closing the lid on my laptop no longer put it to sleep. In fact, no action from within KDE would sleep my laptop; not selecting sleep from the kicker menu, nor selecting it from the power management widget would put my system to sleep.
It seems like it's at least trying to go to sleep. It will deactivate the network like it usually does, but then a moment later it just reconnects, never actually getting as far as sleeping the system. It's not entirely clear to me what part of the chain isn't working, as I'm really not familiar with what all is involved in passing the sleep messages around. It was working one day, and then after a regular weekly full-upgrade it suddenly wasn't. What DOES work: Executing s2ram, s2disk or s2both as root will successfully sleep the system, so the hardware and kernel are all working as expected. -- Tony 'Nicoya' Mantler - Master of Code-fu -- nic...@ubb.ca -- http://www.ubb.ca/ -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5e0d15e7-1c80-4a61-8d48-39c1c8b1c...@ubb.ca
