Am 22.11.25 um 16:26 schrieb Sicelo:
On Fri, Nov 21, 2025 at 10:21:55PM -0500, D Dbg wrote:
/sys/class/power_supply/BAT0/: total 0 drwxr-xr-x 4 root root 0 Nov 21 20:35 . drwxr-xr-x 3 root root 0 Sep 8 2021 .. -rw-r--r-- 1 root root 4096 Nov 21 20:35 alarm -r--r--r-- 1 root root 4096 Sep 3 14:39 cycle_count lrwxrwxrwx 1 root root 0 Sep 3 14:38 device -> ../../../PNP0C0A:02 -r--r--r-- 1 root root 4096 Nov 21 20:35 energy_now drwxr-xr-x 3 root root 0 Sep 8 2021 hwmon1 -r--r--r-- 1 root root 4096 Sep 3 14:39 manufacturer -r--r--r-- 1 root root 4096 Sep 3 14:39 model_name drwxr-xr-x 2 root root 0 Nov 21 20:35 power -r--r--r-- 1 root root 4096 Nov 21 20:35 power_now -r--r--r-- 1 root root 4096 Sep 3 14:38 present -r--r--r-- 1 root root 4096 Sep 3 14:39 serial_number -r--r--r-- 1 root root 4096 Sep 3 14:38 status lrwxrwxrwx 1 root root 0 Sep 8 2021 subsystem -> ../../../../../../../../../class/power_supply -r--r--r-- 1 root root 4096 Sep 3 14:39 technology -r--r--r-- 1 root root 4096 Sep 3 14:38 type -rw-r--r-- 1 root root 4096 Sep 8 2021 uevent -r--r--r-- 1 root root 4096 Sep 3 14:39 voltage_min_design -r--r--r-- 1 root root 4096 Sep 3 14:39 voltage_now
In addition to the already provided information, it might be useful to also attach the output of: cat /sys/class/power_supply/BAT0/uevent
Tbh, this looks more like a kernel / driver problem, not so much a upower issue.
You said that you don't have a battery, yet the kernel apparently thinks otherwise and gives userspace/upowerd this information about BAT0.
upower is just a very small layer on top of what's provided by the kernel.
OpenPGP_signature.asc
Description: OpenPGP digital signature
