Sysprof has a functionality to changed the power profile using power-profiles-daemon. That uses `hadess.PowerProfiles.switch-profile`, however sysprof fails saying it's not implemented. Reproducible: Always Steps to Reproduce: 1. Run sysprof 2. Use the "record with energy profile" setting 3. Sysprof should crash Actual Results: Sysprof crashes Expected Results: Sysprof should managed to change profiles and keep working
Created attachment 2052179 [details] Sysprof error screenshot
Can you please provide your TuneD version and a version of power-profiles-daemon for which the functionality works? I just swapped tuned-2.24.0-1.fc40 for power-profiles-daemon-0.21-3.fc40, and I'm getting the same same error message with both installed. In general, users of power-profiles-daemon or tuned-ppd should switch the profile either via the DBus property ActiveProfile or via the pair of functions HoldProfile and ReleaseProfile.
My bad, forgot the version data. tuned-2.24.0-3.fc41.noarch tuned-ppd-2.24.0-3.fc41.noarch sysprof-47.0-1.fc41.x86_64 > version of power-profiles-daemon for which the functionality works I assumed the functionality worked on ppd and it got broken with tuned-ppd though? I guess then that sysprof has been broken for a while? > In general, users of power-profiles-daemon or tuned-ppd should switch the profile either via the DBus property ActiveProfile or via the pair of functions HoldProfile and ReleaseProfile. Well that would mean that `switch-profile` used to exist in ppd but it doesn't anymore and it's broken on both ppd and tune-ppd. If that's so, I guess I should fil a bug in sysprof instead.
I took a deeper look, and I would classify this as a bug in both tuned-ppd and power-profiles-daemon, not in sysprof. Tuned-ppd now has an upstream fix [1] pending, which resolves this by unifying the polkit policy action names with power-profiles-daemon. Power-profiles-daemon should likely have a bug reported that commit e33f63c [2] breaks sysprof by changing the name of the polkit policy file from net.hadess.PowerProfiles.policy to power-profiles-daemon.policy (which is IMHO rather unconventional). [1] https://github.com/redhat-performance/tuned/pull/698 [2] https://src.fedoraproject.org/rpms/power-profiles-daemon/c/e33f63c
FEDORA-2025-1c520a4d59 (tuned-2.24.1-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-1c520a4d59
FEDORA-2025-97c3eb9857 (tuned-2.24.1-3.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-97c3eb9857
FEDORA-2025-97c3eb9857 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-97c3eb9857` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-97c3eb9857 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-97c3eb9857 (tuned-2.24.1-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-7cd844862c (tuned-2.24.1-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-7cd844862c
FEDORA-2025-7cd844862c (tuned-2.24.1-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.