Note, /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:01/power_supply doesn't exist before suspend.
So, is this a kernel bug and a upower bug? (ie, should the battery always be exposed and should upower not expose it), or is it just a kernel bug (should it never become exposed). In any case, it makes the power indicator pretty useless in my session, because it always displays my battery as completely empty (both in Unity and gnome-shell)
So, dmesg seems to suggest that my laptop does have a second battery slot, and googling around appears to confirm that too:
[ 4.496990] ACPI: Battery Slot [BAT1] (battery absent)
[ 4.504110] ACPI: Battery Slot [BAT0] (battery present)
However, this battery slot only seems to be fully exposed after resume from suspend.
Here's an excerpt of the output of udevadm info --export-db before suspending:
P: /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 00 /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 00 acpi:PNP0C0A:
E: UDEV_LOG=3
E: DEVPATH=
E: DRIVER=battery
E: MODALIAS=
E: SUBSYSTEM=acpi
P: /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 00/power_ supply/ BAT0 /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 00/power_ supply/ BAT0 NAME=BAT0 STATUS= Full PRESENT= 1 TECHNOLOGY= Li-ion CYCLE_COUNT= 0 VOLTAGE_ MIN_DESIGN= 11250000 VOLTAGE_ NOW=12816000 CURRENT_ NOW=1000 CHARGE_ FULL_DESIGN= 8400000 CHARGE_ FULL=8400000 CHARGE_ NOW=8400000 MODEL_NAME= DELL M1RPP14 MANUFACTURER= Samsung SDI SERIAL_ NUMBER= 6116 power_supply
E: UDEV_LOG=3
E: DEVPATH=
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: SUBSYSTEM=
P: /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 01 /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 01 acpi:PNP0C0A:
E: UDEV_LOG=3
E: DEVPATH=
E: DRIVER=battery
E: MODALIAS=
E: SUBSYSTEM=acpi
And after suspending:
P: /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 00 /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 00 acpi:PNP0C0A:
E: UDEV_LOG=3
E: DEVPATH=
E: DRIVER=battery
E: MODALIAS=
E: SUBSYSTEM=acpi
P: /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 00/power_ supply/ BAT0 /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 00/power_ supply/ BAT0 NAME=BAT0 STATUS= Full PRESENT= 1 TECHNOLOGY= Li-ion CYCLE_COUNT= 0 VOLTAGE_ MIN_DESIGN= 11250000 VOLTAGE_ NOW=12816000 CURRENT_ NOW=1000 CHARGE_ FULL_DESIGN= 8400000 CHARGE_ FULL=8400000 CHARGE_ NOW=8400000 MODEL_NAME= DELL M1RPP14 MANUFACTURER= Samsung SDI SERIAL_ NUMBER= 6116 power_supply
E: UDEV_LOG=3
E: DEVPATH=
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: SUBSYSTEM=
P: /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 01 /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 01 acpi:PNP0C0A:
E: UDEV_LOG=3
E: DEVPATH=
E: DRIVER=battery
E: MODALIAS=
E: SUBSYSTEM=acpi
P: /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 01/power_ supply/ BAT1 /devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 01/power_ supply/ BAT1 NAME=BAT1 PRESENT= 0 power_supply
E: UDEV_LOG=3
E: DEVPATH=
E: POWER_SUPPLY_
E: POWER_SUPPLY_
E: SUBSYSTEM=
Note, /sys/devices/ LNXSYSTM: 00/device: 00/PNP0C0A: 01/power_ supply doesn't exist before suspend.
So, is this a kernel bug and a upower bug? (ie, should the battery always be exposed and should upower not expose it), or is it just a kernel bug (should it never become exposed). In any case, it makes the power indicator pretty useless in my session, because it always displays my battery as completely empty (both in Unity and gnome-shell)