Bug 444277 - Incorrect charge stop percentage shown (percentage copied from first battery "BAT0")
Summary: Incorrect charge stop percentage shown (percentage copied from first battery ...
Status: RESOLVED DUPLICATE of bug 430964
Alias: None
Product: Powerdevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.23.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-23 15:55 UTC by dnl
Modified: 2021-10-25 20:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Incorrect charge_stop_threshold value for the second and mouse battery (225.55 KB, image/png)
2021-10-23 15:55 UTC, dnl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dnl 2021-10-23 15:55:46 UTC
Created attachment 142797 [details]
Incorrect charge_stop_threshold value for the second and mouse battery

SUMMARY

The incorrect charge stop percentage is shown for all except the first battery.

The battery at /sys/class/power_supply/BAT0 has set its charge_stop_threshold to 50% and /sys/class/power_supply/BAT0 to 72%, but all batteries (as well as my mouse battery) show the percentage as 50% which is incorrect.

Also it shows both batteries as charging even though they're not charging, status is "Unknown"

See the attached screenshot

STEPS TO REPRODUCE
1. Have multiple batteries in your system
2. Click on the battery tray icon

OBSERVED RESULT

All charge stop percentages are the same as BAT0


EXPECTED RESULT

The first is 50% which is correct, but the second should be 72 % and the mouse doesn't even have a charge_stop_threshold value so it should not show any percentage.

SOFTWARE/OS VERSIONS
 
Linux/KDE Plasma: 5.23.0 
KDE Plasma Version:  5.23.0 
KDE Frameworks Version: 5.87.0
Qt Version: 5.13.3

ADDITIONAL INFORMATION
This was tested on KDE Neon 


Thanks
Comment 1 Nate Graham 2021-10-25 20:39:54 UTC

*** This bug has been marked as a duplicate of bug 430964 ***