close_battery() is called after open_battery() fails, which obviously won't work! (close_battery() attempts to free unallocated memory; glibc detects info[x] is an invalid pointer)
A race condition exists between enumeration and reading of attributes, this is triggered in my case by the ACPI BIOS randomally making the battery disappear and reappear whilst transitioning between AC/Battery, it's much more likely to occur with multiple batteries due to the larger window . ** Patch added: "cpufreqd-2.4.2-battery-crash.patch" https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/260567/+attachment/2955256/+files/cpufreqd-2.4.2-battery-crash.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/260567 Title: cpufreqd crashed on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/260567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
