No battery information available after zypper dup

[MarcusE1W]

After a recent update ~10-15 days ago my system doesn’t have battery information anymore.
The icon in plasma is constantly the one for no battery, red frame and charging symbol.
The actual physical charging still works fine as can be seen with Ubuntu on another partition.

upower -i /org/freedesktop/UPower/devices/battery_qcom_battmgr_bat
  native-path:          qcom-battmgr-bat
  power supply:         yes
  updated:              Sun 08 Mar 2026 17:12:13 GMT (12 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               unknown
    warning-level:       none
    energy:              0 Wh
    energy-empty:        0 Wh
    energy-full:         0 Wh
    energy-full-design:  0 Wh
    energy-rate:         0 W
    charge-cycles:       N/A
    percentage:          0%
    icon-name:          'battery-missing-symbolic'

I use:

• Thinkpad X13s with aarch64 Snapdragon 8cx gen 3 CPU
• Tumbleweed
• Kernel: 6.19.3
• Plasma: 6.6

It could be that it started with kernel 6.19, not 100% sure, though.

Any ideas?
Or what can I do to analyse this further ?

[knurpht]

Not seeing that here on a Thinkpad P16s. What you don’t mention is whether this is Wayland or X11

[MarcusE1W]

It’s Wayland. But considering the result from upower, I don’t think it’s GUI related.

[ATmega328P]

I have the exact same issue on my X13s, just installed OpenSUSE and followed the instructions to install and activate pd-mapper, no change.

upower -i /org/freedesktop/UPower/devices/battery_qcom_battmgr_bat

Yields identical results

[MarcusE1W]

So I thought I just try to install tlpas power manager and see if that resolves anything.
When I did that I noticed that i had power-profiles-daemonand tunedinstalled at the same time, this is apparently not a good idea. The thing is that I did not install tuned.
However, the hope that removing tunedcould solve the issue was unfounded.
I also installed tlpjust for good measure, but this also did not work. No solution yet.

I just thought you could check if you have tunedand power-profiles-daemoninstalled at the same time as well.

[MarcusE1W]

Another observation, could these messages in dmesgbe related ?

[    7.334225] [    T794] synth uevent: /devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-ac: failed to send uevent
[    7.334234] [    T794] power_supply qcom-battmgr-ac: uevent: failed to send synthetic uevent: -11
[    7.334482] [    T794] synth uevent: /devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-bat: failed to send uevent
[    7.334486] [    T794] power_supply qcom-battmgr-bat: uevent: failed to send synthetic uevent: -11
[    7.334720] [    T794] synth uevent: /devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-usb: failed to send uevent
[    7.334724] [    T794] power_supply qcom-battmgr-usb: uevent: failed to send synthetic uevent: -11
[    7.334952] [    T794] synth uevent: /devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-wls: failed to send uevent
[    7.334956] [    T794] power_supply qcom-battmgr-wls: uevent: failed to send synthetic uevent: -11

[ATmega328P]

So I do have both tuned and power-profiles-daemon installed, both were installed automatically when installing OpenSUSE

[ATmega328P]

I think that this is very relevant, if I literally run sudo dmesg the entire screen fills with very similar errors happening constantly

[  614.715575] [   T2095] synth uevent: /devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-bat: failed to send uevent
[  614.715583] [   T2095] synth uevent: /devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-bat: failed to send uevent
[  614.715591] [   T2095] synth uevent: /devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-bat: failed to send uevent
[  614.715599] [   T2095] synth uevent: /devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-bat: failed to send uevent

I think that these point to a driver issue in the kernel, or both of our laptops are in an unknown firmware state that the driver can’t/doesn’t know how to handle.