As far as I could tell from the code, Anoop P B has the correct solution (which I can see from the output of my g-p-m).
If the battery profile of the (primary) battery isn't good enough (accuracy less than 40%), no action will be taken, and no warnings will be shown. This is true even if use_time_for_policy is disabled, which is just plain stupid. It's also quite unacceptable for most cases, since it can cause both data loss and file system corruption if the user doesn't shut down manually in time. I'm going to make an attempt to fix this later tonight (I'm at work right now) by adding two things: 1. A check that takes actions even with a "bad" profile when use_time_for_policy is disabled. 2. A fallback that will use the percentage instead of time if the profile isn't good enough yet. If I'm successful, of course I will submit my patch. I think this bug is actually quite critical since it only affects new users. (New users of gnome, that is. I recently switched from KDE.) -- [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
