Remaining battery power not displaying on the desktop

[rossworsdale]

Hi everyone,

I have an issue where the remaining battery power does not correctly display on my desktop (bottom right next to the clock).

However, when I click on the Power Settings, then Batteries, it displays the correct current charge.

Please see the attached screenshot to illustrate my problem. In the screenshot, you can see that in Power Settings it correctly shows 58% charge whereas the indicator on the desktop next to the clock shows 85%.

Does anyone have an idea how I could fix this issue?

Many thanks in advance.

Ross

[rossworsdale]

Below is the extract from inxi -Fxxxrz
Many thanks,
Ross

ross@ross-Aspire-5560:~$ inxi -Fxxxrz
System:
Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: LightDM 1.30.0
Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal
Machine:
Type: Laptop System: Acer product: Aspire 5560 v: 0.1 serial: <filter>
Chassis: type: 9 v: 0.1 serial: <filter>
Mobo: Acer model: Aspire 5560 v: A11 serial: <filter> UEFI: Phoenix
v: 1.15 date: 12/05/2011
Battery:
ID-1: BAT0 charge: 6.9 Wh condition: 48.8/48.8 Wh (100%) volts: 10.9/11.1
model: LION type: Unknown serial: <filter> status: Discharging
CPU:
Topology: Quad Core model: AMD A6-3420M APU with Radeon HD Graphics
bits: 64 type: MCP arch: Fusion L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 11977
Speed: 801 MHz min/max: 800/1500 MHz boost: enabled Core speeds (MHz):
1: 801 2: 816 3: 800 4: 801
Graphics:
Device-1: AMD Sumo [Radeon HD 6520G] vendor: Acer Incorporated ALI
driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:9647
Display: x11 server: X.Org 1.20.9 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
OpenGL: renderer: AMD SUMO (DRM 2.50.0 / 5.4.0-72-generic LLVM 11.0.0)
v: 3.3 Mesa 20.2.6 compat-v: 3.1 direct render: Yes
Audio:
Device-1: AMD BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G
series]
vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel
bus ID: 00:01.1 chip ID: 1002:1714
Device-2: AMD FCH Azalia vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1022:780d
Sound Server: ALSA v: k5.4.0-72-generic
Network:
Device-1: Broadcom and subsidiaries NetLink BCM57785 Gigabit Ethernet PCIe
vendor: Acer Incorporated ALI driver: tg3 v: 3.137 port: 2100
bus ID: 01:00.0 chip ID: 14e4:16b5
IF: enp1s0f0 state: down mac: <filter>
Device-2: Broadcom and subsidiaries BCM43227 802.11b/g/n vendor: Foxconn
driver: wl v: kernel port: 2100 bus ID: 02:00.0 chip ID: 14e4:4358
IF: wlp2s0 state: up mac: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 59.30 GiB (12.7%)
ID-1: /dev/sda vendor: Hitachi model: HTS547550A9E384 size: 465.76 GiB
speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> rev: A60A scheme: GPT
Partition:
ID-1: / size: 456.96 GiB used: 59.30 GiB (13.0%) fs: ext4 dev: /dev/sda2
Sensors:
System Temperatures: cpu: 44.6 C mobo: 43.0 C gpu: radeon temp: 45 C
Fan Speeds (RPM): N/A
Repos:
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http://ftp.halifax.rwth-aachen.de/linuxmint ulyssa main upstream import backport
2: deb http://ftp-stud.hs-esslingen.de/ubuntu focal main restricted universe multiverse
3: deb http://ftp-stud.hs-esslingen.de/ubuntu focal-updates main restricted universe multiverse
4: deb http://ftp-stud.hs-esslingen.de/ubuntu focal-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
Processes: 191 Uptime: 21h 37m Memory: 3.33 GiB used: 1.27 GiB (38.1%)
Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash
v: 5.0.17 running in: gnome-terminal inxi: 3.0.38
ross@ross-Aspire-5560:~$

[rossworsdale]

Hello,

Possibly the issue is solved now... The numbers are now aligned between power management and what is shown on the desktop.

I have no idea what changed. But I'm happy it appears to be solved.

Thanks,
Ross