Where is battery indicator?

English Applications
#1

Hi,

I’m using opensuse leap 42.3 gnome desktop. I can not find battery indicator on my desktop.

Thanks

#2

Hi
Do you have a custom theme/icons or extensions installed?

If you run the following command, what is the output;


upower -d
#3

Hi,

The output of upower -d is at following:


myname@linux-tndx:~> upower -d
Device: /org/freedesktop/UPower/devices/line_power_ACAD
  native-path:          ACAD
  power supply:         yes
  updated:              2017-12-18 monday 21:05:20 (485 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/DisplayDevice
  power supply:         no
  updated:              2017-12-18 monday 21:05:25 (485 seconds ago)
  has history:          no
  has statistics:       no
  unknown
    warning-level:       none
    icon-name:          ''

Daemon:
  daemon-version:  0.99.4
  on-battery:      no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: Hibernate
myname@linux-tndx:~>

Thanks.

#4

Hi
So what hardware is this, the battery is actually ok? No BIOS settings for battery?

#5

My battery is working, when I unplug the power, my laptop still working.

There’s no BIOS settings for battery.

#6

Hi
This sounds like fairly new hardware since your also having screen brightness issues?

If you fire up YaST bootloader and in the kernel command line options add;


acpi_osi="!Windows2012"

Then reboot, does this help?

Ref: http://redsymbol.net/linux-kernel-boot-parameters/

#7

Hi,

I have done what you said. No effect.

Thanks.

#8

Hi
Sounds like it might be bug report time…

openSUSE:Submitting bug reports - openSUSE

Please post back the bug reference, I would also add the output from the command dmidecode to the report.

#9

Hi,

I have report my problems as bug at here

Thanks

#10

Hi
Run the command (as root user);


dmidecode

Then attach the output to the bug report :wink:

#11

Hi,

Does anyone help?

I searched on internet, I found someone have this kind of issue use method of modifying
DSDT file and including the DSDT file into kernel and recompiling the kernel. But I could not
follow this way because I could not find OperationRegion (EMEM, SystemMemory, 0×FF808001, 0×FF) in
DSDT.dsl, which is in their posts