I'm wondering if HAL is completely to blame for this behavior. Take this with a grain of salt because I don''t know exactly where HAL sits in the stack of things, but I've noticed today that the output of 'cat /proc/acpi/battery/BAT1/*' shows that the 'remaining capacity' line is no longer reporting correctly as I thought it had been previously. Is this a HAL deficiency? I thought the /proc tree didn't have much, if anything to do with HAL.
I've been noticing some inconsistency in behavior on this bug, including an apparent memory leak I mentioned in #196688. It seems the sequence of events is: 1- Boot up laptop. 2- GPM does not report drain correctly, including displaying on the battery icon even when on AC. At this point "/proc/acpi/battery/BAT1/*" "remaining capacity" is also stuck at the level the machine was presumably at when it booted. 3- Changing power state (plugging in and removing AC) a few times seems to kick it into a more correct state, with the GPM icon correctly toggling between AC and BAT, though still not showing changes in charge level. "Remaining Capacity" in /proc/... is now updating. 4- Usually at this point GPM runs away and consumes all available RAM and swap until it is killed, as I describe in #196688. This seems to be getting to be a fairly complex problem. Any thoughts? I'll be trying Daniel's packages and see what they do. -- 01_proc_sys_batteries.patch causes a regression making gnome-power-manager not detect the battery properly https://bugs.launchpad.net/bugs/194719 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
