https://bugs.kde.org/show_bug.cgi?id=496772
--- Comment #4 from redford <redf...@dragonsector.pl> --- (In reply to John Kizer from comment #3) > I'm not an expert by any means, but I believe on Arch you need both the > powerdevil package installed, and the plasma-powerdevil.service user service > enabled and started, for Plasma to be able to successfully manage power > consumption profiles. If you want to manage via KDE, then both should be > setup (perhaps one of those recent updates somehow messed up the > plasma-powerdevil service on your device?) Ah, actually, I have `plasma-powerdevil.service`, I was running from root and didn't expect that the service won't be visible there at all, even with list-units. The logs contain some errors: ``` Nov 28 00:26:10 laptop org_kde_powerdevil[1652]: org.kde.powerdevil: [DDCutilDetector]: Failed to initialize callback Nov 28 00:26:11 laptop systemd[1253]: Started Powerdevil. Nov 28 02:25:08 laptop org_kde_powerdevil[1652]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getconservationmode failed "Battery conservation mode is not supported" Nov 28 02:25:08 laptop org_kde_powerdevil[1652]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getconservationmode failed "Battery conservation mode is not supported" Dec 01 23:15:14 laptop org_kde_powerdevil[1652]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getconservationmode failed "Battery conservation mode is not supported" ``` Doesn't seem related to the profile change, but I guess it explains why since recently my "stop charging at" settings got reset to 100%. > For context, power-profiles-daemon is an upstream project, and is the > underlying service that manages the profiles and their application - take a > look at > https://wiki.archlinux.org/title/CPU_frequency_scaling#power-profiles-daemon > and https://wiki.archlinux.org/title/KDE#Power_management for more info > related to Arch. Thanks for the links! > Without powerdevil running, you should be able to narrow it down by testing > out power-profiles-daemon directly with the command `powerprofilesctl set > performance`. If running that, closing/reopening the lid, then checking > again with the command `powerprofilesctl` shows the issue still happening, > then it's some interaction between your device's firmware and > power-profiles-daemon upstream. Can you try that and see if the issue still > reproduces? Yup, the issue still reproduces after doing that. I didn't know that the firmware could change the profile preset I chose in the OS, I thought this is a feature of the OS, not the firmware? Is this actually an ACPI feature? If so, then I guess I need to contact Lenovo support... -- You are receiving this mail because: You are watching all bug changes.
