Summary Battery Threshold Persistence Issue Description My laptop supports setting the maximum charge threshold at which the battery stops charging. I found this option in System Settings > Power Management > Advanced Power Settings. It allows users to set a Charge Limit and stop charging at the specified value (usually 80%). This feature works as intended, but the setting does not persist after a reboot; it resets to 100%. As a workaround, I created a script as follows: ```bash #!/bin/bash echo 80 | sudo tee /sys/class/power_supply/BAT1/charge_control_end_threshold > /dev/null ``` I added this script to `~/.bash-profile` and configured it to execute without sudo by editing the sudoers file with `visudo`. However, I expected this setting to persist across boots out of the box. Steps to Reproduce 1. Go to System Settings > Power Management > Advanced Power Settings. 2. Set the Charge Limit to 80%. 3. Reboot the laptop. 4. Check the charge limit again; it should reset to 100%. Expected Result The charge limit should persist across reboots. Actual Result The charge limit resets to 100% after rebooting. Environment Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.4 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.15.9-201.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 6 × 11th Gen Intel® Core™ i5-11400H @ 2.70GHz Memory: 8 GiB of RAM (7.5 GiB usable) Graphics Processor 1: Intel® UHD Graphics Graphics Processor 2: NVIDIA GeForce RTX 3050 Laptop GPU Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS TUF Gaming F15 FX506HC_FX506HC System Version: 1.0
I understand that this bug may be difficult to reproduce on other machines. I can provide with relevant logs in case anyone takes this up. Thank you.
It's an issue with ASUS laptops specifically; see Bug 450551. There are efforts afoot to fix it in our side, though. *** This bug has been marked as a duplicate of bug 450551 ***
(In reply to Nate Graham from comment #2) > It's an issue with ASUS laptops specifically; see Bug 450551. Oh. Okay. > There are efforts afoot to fix it in our side, though. Nice to know. Thanks.