+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114)
+--- Thread: Manjaro - No battery info after plugged in (/showthread.php?tid=10332)
Manjaro - No battery info after plugged in - AlecM - 06-18-2020
Just got my Pinebook, basically haven't changed anything from the stock Manjaro that came with it besides updating.
When I plug it in, the battery indicator disappears from the system tray, and the values in the Energy Consumption Statistics menu stops being updated. Even after I unplug it from the charger, the data continues to not update, and I have no way to check battery level. Battery level is set to always show in Configure System Tray. Power settings respond as expected to plugging/unplugging (screen dims when unplugged, brightens when plugged back in).
After a reboot things return to normal.
RE: Manjaro - No battery info after plugged in - xmixahlx - 06-19-2020
it seems that the manjaro default os has some problems with plugins, see this thread:
https://forum.pine64.org/showthread.php?tid=10219&highlight=upower
RE: Manjaro - No battery info after plugged in - AlecM - 06-19-2020
OK, good to know it's at least a known issue and not something I can fix on my own, so I can stop trying to solve it. Thanks.
RE: Manjaro - No battery info after plugged in - spikerguy - 06-19-2020
It was a new bug in latest kde plasma 5.19, Should have been fixed by now but it will take few days to arrive at stable branch.
RE: Manjaro - No battery info after plugged in - zer0sig - 09-16-2020
I am running Manjaro 20.09 on a PBP I received on Monday. The battery says 0% and thinks it will never finish charging, though it keeps running when I unplug it.
I swapped from USB-C to the barrel connector and it looks like it is charging - but it clearly wasn't at 0% before. Anyone know if Manjaro or something in the circuitry are setup to report the battery lower, if for some reason the charging info is inaccurate with USB-C charging, or if something else is the issue?