After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 774719 - Often I am required to unplug and replug the power cable for the indicator to register that my machine is fully charged
Often I am required to unplug and replug the power cable for the indicator to...
Status: RESOLVED INCOMPLETE
Product: gnome-shell
Classification: Core
Component: system-status
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2016-11-19 14:38 UTC by Inactive account
Modified: 2019-02-27 20:13 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22


Description Inactive account 2016-11-19 14:38:48 UTC 
I often find that when I have the power cable plugged into my laptop and it is charging, the indicator in the top-right-hand corner will indicate that I have 0:03 or 0:02 in terms of time left before my laptop is fully charged, but it will get stuck on this and never go beyond that nor show that it is fully charged, however if I in one of these instances unplug and then replug by laptop it will immediately show as fully charged.

So it's almost as though it needs some sort of refresh or prompt and gets stuck otherwise. This is not always the case, but it is in most cases.

I am running Ubuntu GNOME 16.10 with GNOME 3.22.

Related: Bug #774717

I initially reported this bug here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1643190 But thought I should also do so upstream.
Comment 1 Florian Müllner 2016-11-19 15:28:51 UTC 
When this happens, what is the output of
$ gdbus call --system --dest org.freedesktop.UPower \
             --object-path /org/freedesktop/UPower/devices/DisplayDevice \
             --method org.freedesktop.DBus.Properties.Get 'org.freedesktop.UPower.Device' 'TimeToFull'
Comment 2 Florian Müllner 2019-02-27 20:13:52 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!