On Sun, Sep 07, 2025 at 08:08:02PM +0100, James Addison wrote: > Package: src:linux > Version: 6.16.3-1 > Severity: normal > > Dear Maintainer, > > There is a possibility that my laptop's battery is in a degrated state of > health; if this issue is determined to be a hardware problem, then my > apologies > in advance for time spent debugging. > > Recently I have noticed that the battery power indicator in my GNOME desktop > environment frequently indicates a 0% charge level, despite the fact that the > laptop can continue without AC power for some time. > > I've been using the upower utility (from the binary package of the same name) > to report in-use battery statistics, and receive inconsistent results. > > The most recent results, as I write this, are shown below: > > $ sudo upower -i /org/freedesktop/UPower/devices/battery_BAT0 > native-path: BAT0 > vendor: LGC > model: 00HW028 > serial: 65535 > power supply: yes > updated: Sun Sep 7 20:01:12 2025 (7 seconds ago) > has history: yes > has statistics: yes > battery > present: yes > rechargeable: yes > state: pending-charge > warning-level: none > energy: 0 Wh > energy-empty: 0 Wh > energy-full: 43.41 Wh > energy-full-design: 50.54 Wh > voltage-min-design: 15.2 V > capacity-level: Critical > energy-rate: 0 W > charge-cycles: N/A > percentage: 0% > capacity: 85.8924% > technology: lithium-polymer > charge-start-threshold: 75% > charge-end-threshold: 80% > charge-threshold-enabled: yes > charge-threshold-supported: yes > icon-name: 'battery-caution-charging-symbolic' > History (charge): > 1757271651 0.000 unknown > History (rate): > 1757271651 0.000 unknown > > > In previous boots of the system earlier today, I have encountered 0 Wh values > simultaneously for both the energy-full and energy-full design fields. > > I do not recall encountering the 0% battery status indicator before upgrading > to Debian trixie -- however, it is also possible that the physical state of > the > battery has degraded within that same time window.
Can you please retest with the bookworm kernel? If there the problem
doesn't occur it's most likely a regression, if not, it's probably your
hardware that has a problem.
To do that just temporarily readd the bookworm URLs back to apt if
necessary (something like:
$ cat /etc/apt/sources.list.d/deb12-bookworm.sources
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: bookworm
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-bookworm-stable.gpg
Types: deb
URIs: http://deb.debian.org/debian/
Suites: bookworm-updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-bookworm-automatic.gpg
Types: deb
URIs: http://debug.mirrors.debian.org/debian-debug/
Suites: bookworm-debug
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-bookworm-stable.gpg
Types: deb
URIs: https://security.debian.org/debian-security
Suites: bookworm-security
Components: main contrib non-free non-free-firmware
Signed-by:
/usr/share/keyrings/debian-archive-bookworm-security-automatic.gpg
), install linux-image-6.1.0-39-amd64 and boot into that kernel.
Best regards
Uwe
signature.asc
Description: PGP signature
