Late battery notification

[István Papp]

I don't know the correct package for this bug, and it was pretty hard to get to this point in the bug reporting process.

I got a battery notification at 0% battery, moments before my laptop shut down. I would like to get notifications earlier, around 10-15% charge, so I can say goodbye to my colleagues in the meeting, or reach a power cable in time.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-41.41-generic 6.5.13
Uname: Linux 6.5.0-41-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 25 13:43:18 2024
DistUpgraded: 2023-10-26 16:16:54,401 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2279]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-26 (243 days ago)
dmi.bios.date: 02/22/2024
dmi.bios.release: 1.82
dmi.bios.vendor: LENOVO
dmi.bios.version: N2IETA4W (1.82 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20N4000KHV
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.26
dmi.modalias: dmi:bvnLENOVO:bvrN2IETA4W(1.82):bd02/22/2024:br1.82:efr1.26:svnLENOVO:pn20N4000KHV:pvrThinkPadT590:rvnLENOVO:rn20N4000KHV:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N4_BU_Think_FM_ThinkPadT590:
dmi.product.family: ThinkPad T590
dmi.product.name: 20N4000KHV
dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590
dmi.product.version: ThinkPad T590
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

I'm not totally sure which component is responsible for this. It looks like it might be a combination of upower and gnome-settings-daemon in which case it looks like there should be a warning at about 10%? Please try charging to more than 10% and letting it run down again to see if that warning happens.

Also note that Ubuntu 23.10 reaches end of life next month so please consider upgrading to Ubuntu 24.04.

[István Papp (number492)]

I managed to unintentionally reproduce the issue, I saw no notification before the one at 0%. I'm upgrading to 24.04 today, then I'll check again.

[Daniel van Vugt (vanvugt)]

A few thoughts:

1. Did you confirm the battery was above 10% at some point before it happened?

2. The cause might be large jumps in the battery's status values causing the normal notifications to get skipped. In my brief time looking at the code it seemed like that might be possible. Did you for example observe a time when it was 11% and 10% and then 9%?

3. I'm not totally sure there is a warning at 10% anyway. I haven't tested running down a battery in a while.

[István Papp (number492)]

1. Yes, I was working for hours, the battery was well over 50% when I started. The whole issue happened multiple times this year, and twice in a day last week.

2. I forgot that the laptop was not plugged in, and only noticed the 0% notification. It is possible that the value jumps, I'll try to reproduce again, on 24.04 this time.

3. There should be, even if the value jumps. That would require keeping state somewhere though, just that the notification was already shown or not, and it would still not handle the case where the value jumps from 20+ directly to 0.