There are a apparently lots of causes for this problem. One cause is the kernel not recognizing the battery properly. If that is the case, then even the "acpi -V" command won't show a battery. However, if that command shows a battery connected, then the problem lies with the hal -> dbus -> gnome-power-manager chain. My problem was the latter, and I just fixed this by
sudo sysv-rc-conf -p Then going to the hal service and changing each S## level to read S99. That made the hal service start after everything else. I don't know if this has any harmful side effects, but I've booted once so far without any hiccups and now gnome-power-manager finally detects the battery properly, and even sleep/suspends/hibernates and shows the brightness applet properly. What I find strange is that I never changed this myself and the hal -> dbus -> gnome-power-manager communication worked fine before. The one thing I did which changed this was to restart dbus manually. Ever since I had done that, gnome-power-manager had failed to detect the battery unless I restarted the hal service. I can't imagine why doing that would have changed anything, but it did. As for the kernel problems, I can't be of any help there. That's a kernel related bug and should probably be filled under the relevant "linux" package. -- ubuntu doesn't notice when running on battery https://bugs.launchpad.net/bugs/39413 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
