Jo, Well make it a week or two. Running the computer with the electrical cord in place does not count (although it does add data about how the battery charges). You can check the progress by right clicking g-p-m in the system tray, selecting "power history" and then in that box (near the bottom), select "discharge time accuracy profile". when the average value of that graph is over 40%, stuff will start working.
What my patch does it fix the gap before it starts working. First and foremost, caring about the profile even when use_time_for_policy is disabled is just weird, since the profile doesn't add anything to the mix at that point. Then, not telling the user anything about this thing with ignoring actions is just a bad idea, there's no warning anywhere. I actually "fell into the trap" myself a few days ago, after installing ubuntu on my new laptop. Thank god no data was lost, because I was in the middle of doing quite a lot. I still think this is a bug, since a developer put in this accuracy check for a good cause (some broken ACPI's could make the computer hibernate way too early, according to the changelog), but probably didn't think about what would happen until the accuracy profile was good enough. And yes, you can enable use_time_for_policy again. -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
