Created attachment 157580 [details] Video showing Start and Stop being reversed STEPS TO REPRODUCE 1. Go to Settings → Advantaged Power Settings 2. Set a Start and Stop threshold for Charge Limit 3. Hit Apply button 4. Navigate away from and then back to the Advantaged Power Settings OBSERVED RESULT The values for Start and Stop threshold are reversed and filed in the in the opposite setting field. EXPECTED RESULT Start and Stop threshold should stay in their respective fields. SOFTWARE/OS VERSIONS Operating System: NixOS 23.05 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.7-zen1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620
*** Bug 463884 has been marked as a duplicate of this bug. ***
Git commit 127f6aef4ec9626e95c200d5600655bc781b45d6 by Jakob Petsovits. Committed on 15/12/2023 at 07:21. Pushed by jpetso into branch 'master'. Drop "Advanced Power Settings" KCM in favor of a new QML page This commit removes the QWidgets-based KCM in kcmodule/global, and instead adds a new QML page accessible via header action in the existing "Energy Saving" (QML) KCM a.k.a. profiles config. Renaming folder and class names of the profiles KCM to reflect its combined scope is left for a later commit. I modified the "Energy Saving" KCM's JSON file to declare it on the top level of System Settings, and merged extra keywords from the now deleted kcm_powerdevilglobalconfig.json. We'll have to remove the "power-management" category from System Settings after this, as only a single KCM is left. New C++ KCM backend code is mostly moved from GeneralPage.{h,cpp}: * PowerDevil::GlobalSettings provides kcm.settings.global for QML. * KAuth-powered ChargeThresholdHelper settings are accessible via kcm.externalServiceSettings & left out of non-default highlighting. * "Supports $X" properties are added to the KCM class directly. All in all, it's a fairly straight port that doesn't change the underlying data representation apart from the obvious C++/QML split. Only the magic value -1 gets replaced by a constant named ChargeThresholdUnsupported, plus functions for checking support. The UI is also roughly the same. That said, there are some differences: * I replaced the "Configure Notifications" button with a column of two ToolButtons in the style of Quick Settings' "Most used pages". * The start-charging threshold, i.e. the lower bound, previously had a weirdly long spinbox field because it needed to fit the "special value" text "Always charge when plugged in". This looks awkward and is not easily discoverable. Furthermore, QQC2.SpinBox doesn't have a concept of a "special value" and doesn't pre-allocate item width for any given space. I decided to represent this state with numeric percentages only. * "Special value" means display text for the minimum value ("from") of a QSpinBox. The start-charging threshold QSpinBox had no minimum set in generalPage.ui, so its "special value" would have been 0. This makes little sense, "Always charge" for the start threshold is conceptually more similar to "start threshold equals stop threshold". * Hence, the start threshold SpinBox now starts at 1, not 0, and the maximum allowed value is that of the stop threshold from the other field above. If the maximum value is selected, we write the "special value" 0 to the backend. If the backend value changes to 0, we set the UI to the stop threshold value. Related: bug 449254, bug 450276, bug 459081 M +0 -2 kcmodule/CMakeLists.txt M +0 -1 kcmodule/common/CMakeLists.txt D +0 -90 kcmodule/common/ErrorOverlay.cpp D +0 -28 kcmodule/common/ErrorOverlay.h D +0 -19 kcmodule/global/CMakeLists.txt D +0 -266 kcmodule/global/GeneralPage.cpp D +0 -47 kcmodule/global/GeneralPage.h D +0 -4 kcmodule/global/Messages.sh D +0 -277 kcmodule/global/generalPage.ui D +0 -126 kcmodule/global/kcm_powerdevilglobalconfig.json M +3 -1 kcmodule/profiles/CMakeLists.txt A +190 -0 kcmodule/profiles/ExternalServiceSettings.cpp [License: GPL(v2.0+)] A +66 -0 kcmodule/profiles/ExternalServiceSettings.h [License: GPL(v2.0+)] M +0 -2 kcmodule/profiles/Messages.sh M +107 -5 kcmodule/profiles/ProfilesConfigKCM.cpp M +41 -2 kcmodule/profiles/ProfilesConfigKCM.h M +32 -31 kcmodule/profiles/kcm_powerdevilprofilesconfig.json A +364 -0 kcmodule/profiles/ui/GlobalConfig.qml [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] A +53 -0 kcmodule/profiles/ui/MostUsedItem.qml [License: LGPL(v2.0)] M +8 -1 kcmodule/profiles/ui/main.qml https://invent.kde.org/plasma/powerdevil/-/commit/127f6aef4ec9626e95c200d5600655bc781b45d6
To be honest, this sounds more like a system issue or perhaps an issue with the PowerDevil charge threshold helper. That said, Plasma 6 Beta 2 has new UI code for setting charge limits, so if the UI itself had an issue, there's a high chance this is fixed now. Please retest once you have access to a Plasma 6 setup. Thanks!