Bug 505048 - The battery charge limit is not preserved across reboots
Summary: The battery charge limit is not preserved across reboots
Status: RESOLVED DUPLICATE of bug 450551
Alias: None
Product: plasmashell
Classification: Plasma
Component: Power and Battery widget (other bugs)
Version First Reported In: 6.3.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-31 10:35 UTC by Lech
Modified: 2025-06-01 13:52 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lech 2025-05-31 10:35:42 UTC
SUMMARY

The battery charge limit is not preserved across reboots. Setting to, eg. 80% works until the reboot, when it has to be reset again manually, otherwise it is at 100%.

In addition, setting it to 80% is not easy. Deleting "100%" in the entry text box and entering anything, or backspacing on 2 characters of "100%" causes it to fill up with "50%", while it should just fill up with the value I enter or allow me to backspace everything. Then, editing the "50%" is normal.

STEPS TO REPRODUCE
1. Open the Power and Battery widget
2. Click on "Configure Power Management" icon
3. Click on "Advanced Power Settings"
4. Change (or try to change) the "Charge Limit"
5. Apply
6. Reboot

OBSERVED RESULT

1) The manually set charge limit does not persist across the reboots (on, for example, Gnome, it does)
2) The text box for entering the charge limit does not work as expected

EXPECTED RESULT

1) The charge limit persist across reboots
2) The charge limit textbox works like a standard textbox, not overwriting what a user tries to do

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 42
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Comment 1 cwo 2025-05-31 18:36:05 UTC
Thank you for the bug report!

Having multiple issues in one report makes them hard to track. (I can reproduce the second but not the first, so I can't confirm this report as is, but I could if they were separate.) Let's use this one for the battery charge limit not being preserved. Please file a separate report for the spinbox entry field being hard to use, in product "systemsettings", component "kcm_powerdevil".
Comment 2 Lech 2025-05-31 18:44:24 UTC
(In reply to cwo from comment #1)
> Thank you for the bug report!
> 
> Having multiple issues in one report makes them hard to track. (I can
> reproduce the second but not the first, so I can't confirm this report as
> is, but I could if they were separate.) Let's use this one for the battery
> charge limit not being preserved. Please file a separate report for the
> spinbox entry field being hard to use, in product "systemsettings",
> component "kcm_powerdevil".

Thanks. Submitted. Is there any info I can provide to help with this bug? If you can't reproduce, it may be hardware-dependent, but solvable, as the setting persists on GNOME. However, I am not sure what info I should give you.
Comment 3 cwo 2025-06-01 07:35:10 UTC
(In reply to Lech from comment #2)
> Thanks. Submitted. Is there any info I can provide to help with this bug? If
> you can't reproduce, it may be hardware-dependent, but solvable, as the
> setting persists on GNOME. However, I am not sure what info I should give
> you.

Thanks for filing the separate bug!

I don't know much about the backends of power handling, I'll leave this to the developers with more background in that area. I do think that support for this is likely hardware-specific; on my old thinkpads it works flawlessly,
Comment 4 David Edmundson 2025-06-01 13:52:31 UTC

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