Alright, changing threshold percent levels AND profile/time/policy did the trick for me, so presumably the problem for me lies in the inability to use time policy
- This DID work for me somewhere on alpha6 (see former comment by me [2008-03-31]), and since I have values set to low=1200, crit=300, act=120, then before going down to 8% (time=89) and freezing it should pass all or at least the low and crit thresholds, which should give a notification. Also, I'm getting a slightly weird output from the debug when using only percentage, it seems to drop from 19% to 6% all of a sudden. The computer also has trouble hibernating but that I blame on the debugging, since when doing the same thing without debug it hibernates fine. I'm attaching part of this log, if anybody's interested (which also shows failed hibernation attempts and percentage going down to 0% [which seems to upset gpm a bit]) @Chad Bernier: Holding out until I buy a new laptop. ** Attachment added: "gpm.debug.log2excerpt.txt" http://launchpadlibrarian.net/13126675/gpm.debug.log2excerpt.txt -- [Gutsy] Action on critical battery isn't triggered - regression https://bugs.launchpad.net/bugs/135548 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
