KDE battery indicator. Not detecting the battery

iarest · October 8, 2017, 10:46pm

I have installed and updated the Leap 42.3 on my Toshiba Tecra Z40 and the battery indicator displays that there is no battery available.

After the fresh install, the indicator worked properly just once. Later, after updating the installation, the battery indicator stopped working properly and I have no clue about what’s going on. The battery indicator shows when the AC is plugged, but not the battery percentage itself, just a red cross on the bottom of the icon.

BTW, the percentage is showed correctly on the log in screen. The KDE version is Plasma 5.8.7

Some commands, that maybe could help.

acpi -V


Battery 0: Charging, 94%, 00:25:05 until charged
Battery 0: design capacity 4089 mAh, last full capacity 3350 mAh = 81%
Adapter 0: on-line
Thermal 0: ok, 16.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 107.0 degrees C
Cooling 0: x86_pkg_temp no state information available
Cooling 1: intel_powerclamp no state information available
Cooling 2: Processor 0 of 10
Cooling 3: Processor 0 of 10
Cooling 4: Processor 0 of 10
Cooling 5: Processor 0 of 10

upower -d


Device: /org/freedesktop/UPower/devices/line_power_ADP1
  native-path:          ADP1
  power supply:         yes
  updated:              dom 08 oct 2017 22:05:16 CEST (1948 seconds ago)
  has history:          no
  has statistics:       no
  line-power
    warning-level:       none
    online:              yes
    icon-name:          'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:          BAT1
  model:                G71C000GB310
  serial:               0
  power supply:         yes
  updated:              dom 08 oct 2017 22:37:43 CEST (1 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               charging
    warning-level:       none
    energy:              46,031 Wh
    energy-empty:        0 Wh
    energy-full:         48,522 Wh
    energy-full-design:  59,223 Wh
    energy-rate:         7,153 W
    voltage:             14,48 V
    time to full:        20,9 minutes
    percentage:          94%
    capacity:            81,931%
    technology:          lithium-ion
    icon-name:          'battery-full-charging-symbolic'
  History (charge):
    1507494959  94,000  charging
  History (rate):
    1507495063  7,153   unknown
    1507495061  7,312   charging
    1507495060  8,152   charging
    1507495059  7,717   charging
    1507495058  7,341   charging
    1507495004  6,672   charging

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply:         yes
  updated:              dom 08 oct 2017 22:37:43 CEST (1 seconds ago)
  has history:          no
  has statistics:       no
  battery
    present:             yes
    state:               charging
    warning-level:       none
    energy:              46,031 Wh
    energy-full:         48,522 Wh
    energy-rate:         7,153 W
    time to full:        20,9 minutes
    percentage:          94%
    icon-name:          'battery-full-charging-symbolic'

Daemon:
  daemon-version:  0.99.4
  on-battery:      no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: Hibernate

Any ideas?

Thank you so much.

deano_ferrari · October 9, 2017, 5:13am

Welcome to openSUSE Forums iarest. The output you posted looks as expected to me. Further to this, what does ‘upower -d’ report when the laptop is running on battery?

deano_ferrari · October 9, 2017, 5:25am

When running on battery, what is reported by the following?

acpi -i

Please post all output within

[/COD.] tags (refer to the '#' button in the forum editor).

iarest · October 9, 2017, 10:18am

Thank you for replying

At this moment I’m using the battery and the battery indicator says that I do not have any battery.

The output of **acpi -i
**


Battery 0: Discharging, 87%, 09:15:22 remaining
Battery 0: design capacity 4089 mAh, last full capacity 3350 mAh = 81%

deano_ferrari · October 9, 2017, 10:36am

…and what about the following?

upower -d

iarest · October 9, 2017, 11:05am

I had put it in the first post, that’s why I didn’t post it again. Sorry.


linux-b1qy:~> upower -d     
Device: /org/freedesktop/UPower/devices/line_power_ADP1
  native-path:          ADP1
  power supply:         yes
  updated:              lun 09 oct 2017 10:56:22 CEST (279 seconds ago)
  has history:          no
  has statistics:       no
  line-power
    warning-level:       none
    online:              no
    icon-name:          'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:          BAT1
  model:                G71C000GB310
  serial:               0
  power supply:         yes
  updated:              lun 09 oct 2017 11:00:59 CEST (2 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               discharging
    warning-level:       none
    energy:              39,255 Wh
    energy-empty:        0 Wh
    energy-full:         48,508 Wh
    energy-full-design:  59,223 Wh
    energy-rate:         4,344 W
    voltage:             14,48 V
    time to empty:       9,0 hours
    percentage:          80%
    capacity:            81,9074%
    technology:          lithium-ion
    icon-name:          'battery-full-symbolic'
  History (charge):
    1507539639  80,000  discharging
  History (rate):
    1507539659  4,344   unknown
    1507539658  4,517   discharging
    1507539656  4,865   discharging
    1507539654  5,444   discharging
    1507539652  5,618   discharging
    1507539599  5,133   discharging

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply:         yes
  updated:              lun 09 oct 2017 11:00:59 CEST (2 seconds ago)
  has history:          no
  has statistics:       no
  battery
    present:             yes
    state:               discharging
    warning-level:       none
    energy:              39,255 Wh
    energy-full:         48,508 Wh
    energy-rate:         4,344 W
    time to empty:       9,0 hours
    percentage:          80%
    icon-name:          'battery-full-symbolic'

Daemon:
  daemon-version:  0.99.4
  on-battery:      yes
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: Hibernate

iarest · October 9, 2017, 12:36pm

I have discovered something that maybe could help.

I have rebooted the laptop and logged in and the battery indicator wasn’t working properly (showing that there isn’t any battery). BUT, I closed the user session and logged in again and mysteriously the battery indicator appeared and it had detected the battery.

After that I rebooted again, logged in and the battery indicator was broken again. I tried again to log out and log in, and the indicator detected again the battery.

I have tested it several times and all the times worked in the same way.

deano_ferrari · October 9, 2017, 11:33pm

Try creating a new user, and see if the same issue manifests there as well.

iarest · October 10, 2017, 4:20pm

I have created a new user and it’s the same issue there.

I did some new tests and I found something else. If I wait a bit more in the login screen, and I enter with my user. The battery indicator is working properly. It seems to me that some service starts later than it should be and that’s why if I log out and log in again fixes the problem provisionally.

Of course, it’s just a guess because I don’t know the details of what’s going on there.

deano_ferrari · October 11, 2017, 1:09am

That’s an interesting find. Not sure if this is a PowerDevil issue or D-bus perhaps? A bug report is probably the best course of action here.

gogalthorp · October 11, 2017, 2:40am

run systemctrl blame and see what is starting when and how long

eng-int · October 13, 2017, 10:14am

Excuse me, but what is that meant to do?

y3:~ # systemctrl blame 
If 'systemctrl' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf systemctrl
y3:~ # systemctl blame 
Unknown operation blame.
y3:~ #

I had similar observation to the OP a couple of weeks ago on this Lenovo Yoga-3 Pro Tumbleweed. I never got to the bottom of it and the problem seemed to resolve itself. A colleague’s similar laptop has not exhibit this symptom.

deano_ferrari · October 13, 2017, 10:22am

eng-int:

Excuse me, but what is that meant to do?

y3:~ # systemctrl blame 
If 'systemctrl' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf systemctrl
y3:~ # systemctl blame 
Unknown operation blame.
y3:~ #

I think he actually meant

systemd-analyze blame

but in any case, I doubt that will lead to anything conclusive with this particular issue.

eng-int · October 13, 2017, 10:25am

OK it should be:

rayh@y3:~> systemd-analyze blame

gogalthorp · October 13, 2017, 2:34pm

Might uncover a startup process that runs longer then expected and yes meant systemd-analyse blame . had a mind fart LOL:shame:

virex · August 1, 2018, 6:08pm

i have the same problem on tumbleweed https://bugzilla.opensuse.org/show_bug.cgi?id=1101556
did you have a solution?