desktop-packages team mailing list archive

[MNLipp <379599@xxxxxxxxxxxxxxxxxx>]

I'm still seeing this with my HP 6730b and 11.10. The laptop has an additional removable battery. When I issue
> cat /proc/acpi/battery/BAT1/state

I get

> present:                 no

So it shouldn't be a problem to simply "leave that one out" when making
descisions concerning the battery state.

When I suspend my laptop, unplug the power and then resume again, it
will in about one of two cases shutdown because of low battery, although
the built-in battery is almost at 100% (obviously).

If I remember right, that behaviour started with Natty. Maverick was
still OK.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/379599

Title:
  System shutdown on 0% for 1 of 2 batteries.

Status in Gnome Powermanager:
  In Progress
Status in The Linux Kernel:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-power-manager

  With two batteries, when the first battery hits low levels gnome-
  power-manager alerts the user of low/critical and then takes the
  "critcially" low action, even thow the other battery is still at 100%.
  gnome-power-manager detects and can interact with either battery.

  This affects at least karmic, but is believed to affect jaunty as
  well.

  gnome-power-manager version 2.26.1-0ubuntu3

  I would expect that gnome-power-manager should warn, but then continue
  to move through the second battery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/379599/+subscriptions