Bug 481995

Summary:	Power profiles applet updates power profile, but does not reflect change
Product:	[Unmaintained] Powerdevil	Reporter:	Swiftloke <swiftlokex>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	git, me, natalie_clarius, nate
Priority:	NOR
Version First Reported In:	5.27.8
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	6.1
Sentry Crash Report:

Description Swiftloke 2024-02-29 04:46:55 UTC

SUMMARY
Out of the box, with a fresh install of Kubuntu 23.10, the power profiles applet can update the power profile, but the slider does not update. This means it appears that no change occurred at all. (In fact, I only found out that the change was working after writing out this bug and getting logs!)


STEPS TO REPRODUCE
1. Click on the battery widget in the Plasma desktop bar
2. Attempt to change the power profile, for instance from "balanced" to "performance"

OBSERVED RESULT
Power profile is set, but the bar does not update. The bar changes for a brief moment, then snaps back to its original position.

EXPECTED RESULT
Power profile changes, and the bar updates to reflect the change.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 23.10
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Two people have reported this bug on Reddit in the last month, implying that it's a recent issue:
https://www.reddit.com/r/kde/comments/1b072mp/power_profile_switching_isnt_working_on_kubuntu/
https://www.reddit.com/r/Kubuntu/comments/1ad3yi9/unable_to_set_power_profile_in_kubuntu_2310/

Both of them helpfully recorded videos of the bug in action.

This is a log of the ``power-profiles-daemon`` service running in ``--verbose`` with the faulty behavior, showing that the settings are in fact being updated:

```
● power-profiles-daemon.service - Power Profiles daemon
     Loaded: loaded (/lib/systemd/system/power-profiles-daemon.service; enabled; preset: enabled)
     Active: active (running) since Wed 2024-02-28 21:43:12 MST; 7s ago
   Main PID: 7658 (power-profiles-)
      Tasks: 5 (limit: 27270)
     Memory: 1.5M
        CPU: 47ms
     CGroup: /system.slice/power-profiles-daemon.service
             └─7658 /usr/libexec/power-profiles-daemon --verbose

Feb 28 21:43:12 laptop systemd[1]: Starting power-profiles-daemon.service - Power Profiles daemon...
Feb 28 21:43:12 laptop power-profiles-[7658]: Starting power-profiles-daemon version 0.13
Feb 28 21:43:12 laptop power-profiles-[7658]: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
Feb 28 21:43:12 laptop systemd[1]: Started power-profiles-daemon.service - Power Profiles daemon.
Feb 28 21:43:12 laptop power-profiles-[7658]: Handling driver 'fake'
Feb 28 21:43:12 laptop power-profiles-[7658]: probe() failed for driver fake, skipping
Feb 28 21:43:12 laptop power-profiles-[7658]: Handling driver 'platform_profile'
Feb 28 21:43:12 laptop power-profiles-[7658]: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
Feb 28 21:43:12 laptop power-profiles-[7658]: Monitoring file /sys/devices/platform/thinkpad_acpi/dytc_lapmode for changes
Feb 28 21:43:12 laptop power-profiles-[7658]: ACPI performance_profile is now p, so profile is detected as performance
Feb 28 21:43:12 laptop power-profiles-[7658]: Found a dytc_lapmode sysfs attribute to thinkpad_acpi
Feb 28 21:43:12 laptop power-profiles-[7658]: Handling driver 'intel_pstate'
Feb 28 21:43:12 laptop power-profiles-[7658]: Driver 'platform_profile' already probed, skipping driver 'intel_pstate'
Feb 28 21:43:12 laptop power-profiles-[7658]: Handling driver 'amd_pstate'
Feb 28 21:43:12 laptop power-profiles-[7658]: Driver 'platform_profile' already probed, skipping driver 'amd_pstate'
Feb 28 21:43:12 laptop power-profiles-[7658]: Handling driver 'placeholder'
Feb 28 21:43:12 laptop power-profiles-[7658]: Driver 'platform_profile' already probed, skipping driver 'placeholder'
Feb 28 21:43:12 laptop power-profiles-[7658]: Handling action 'trickle_charge'
Feb 28 21:43:12 laptop power-profiles-[7658]: Applying profile 'performance' from configuration file
Feb 28 21:43:12 laptop power-profiles-[7658]: Setting active profile 'performance' for reason 'reset' (current: 'performance')
Feb 28 21:43:12 laptop power-profiles-[7658]: Can't switch to performance mode, already there
Feb 28 21:43:19 laptop power-profiles-[7658]: Transitioning active profile from 'performance' to 'power-saver' by user request
Feb 28 21:43:19 laptop power-profiles-[7658]: Setting active profile 'power-saver' for reason 'user' (current: 'performance')
Feb 28 21:43:19 laptop power-profiles-[7658]: Writing 'low-power' to '/sys/firmware/acpi/platform_profile'
Feb 28 21:43:19 laptop power-profiles-[7658]: Successfully switched to profile power-saver
Feb 28 21:43:19 laptop power-profiles-[7658]: /sys/firmware/acpi/platform_profile changed (0)
Feb 28 21:43:19 laptop power-profiles-[7658]: ACPI performance_profile is now l, so profile is detected as power-saver
Feb 28 21:43:19 laptop power-profiles-[7658]: /sys/firmware/acpi/platform_profile changed (0)
Feb 28 21:43:19 laptop power-profiles-[7658]: ACPI performance_profile is now l, so profile is detected as power-saver
Feb 28 21:43:19 laptop power-profiles-[7658]: /sys/firmware/acpi/platform_profile changed (1)
Feb 28 21:43:19 laptop power-profiles-[7658]: ACPI performance_profile is now l, so profile is detected as power-saver
```

Comment 1 Nate Graham 2024-03-01 06:24:29 UTC


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

Comment 2 git 2024-04-29 21:09:28 UTC

Happens for me on a fresh Kubuntu 23.10.

The slider snaps back to its previous state, but the profile got actually updated.
The pp daemon is working fine and can be controlled via cli without problems.

This is not a firmware bug and from my knowledge it is still a KDE issue.

Comment 3 Nate Graham 2024-04-29 21:22:00 UTC

Yes, that did indeed turn out to be the case. Thankfully I've confirmed that it's already fixed in Plasma 6.1.