Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Hello,

I am adding similar symptoms and a verified restart recovery from an
Arch/Omarchy installation (not Debian) to this report.

Collected: October 1, 2026
Hardware: Apple MacBookPro12,1
Installed UPower package: 1.91.3-1
Running kernel: 7.2.5-3-omarchy
Battery: SMP bq20z451
Charge cycles: 16

Before restarting UPower, the kernel reported:

POWER_SUPPLY_STATUS=Full
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=11400000
POWER_SUPPLY_CHARGE_FULL_DESIGN=6800000
POWER_SUPPLY_CHARGE_FULL=6876000
POWER_SUPPLY_CHARGE_NOW=6876000
POWER_SUPPLY_CAPACITY=101
AC adapter: POWER_SUPPLY_ONLINE=1

UPower simultaneously reported:

state: fully-charged
energy: 78.3864 Wh
energy-full: 736.634 Wh
energy-full-design: 77.52 Wh
percentage: 10.6412%

The mismatch persisted across multiple readings. The kernel capacity of
101% is itself above 100%, but charge_now equals charge_full. Using
charge_full and voltage_min_design gives 6.876 Ah * 11.4 V = 78.3864 Wh,
rather than 736.634 Wh.

After running only pkexec systemctl restart upower.service, UPower reported:

state: fully-charged
energy-full: 78.3864 Wh
percentage: 100%

The kernel still reported Full, charge_now and charge_full both remained
6876000 uAh, and the adapter remained online. UPower was active and the
desktop shell answered its health ping. No shell restart was performed; the
visual battery widget was not independently checked.

This provides a before/after recovery with unchanged kernel charge values
on another MacBook model and installed UPower version. It appears similar
to the issue described here, though a common root cause has not been
established.