tuned
tuned copied to clipboard
redhat-performance
tuned-ppd: Support the new UPower PPD namespace
Since version 0.20, power-profiles-daemon exposes its DBus interface under "org.freedesktop.UPower.PowerProfiles" alongside the previous name. To be compatible with PPD, this commit implements the same change into tuned-ppd.
Resolves: #683
Please be careful with this, the PPD namespace has other changes that are in flight. See these:
- https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/merge_requests/210
- https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/merge_requests/212
Thanks for the heads up, @superm1. I just had a look at the proposed power-profiles-daemon changes, but I don't see anything that should be an immediate problem for us.
IIUC, you're adding some new functionality to the existing PPD namespace. As of now, tuned-ppd does not aim to cover the entire functionality - we're mostly interested in what's actively used by power management daemons such as powerdevil or gnome-control-center. The new functionality may or may not be added in the future.
Thanks for the heads up, @superm1. I just had a look at the proposed power-profiles-daemon changes, but I don't see anything that should be an immediate problem for us.
IIUC, you're adding some new functionality to the existing PPD namespace. As of now, tuned-ppd does not aim to cover the entire functionality - we're mostly interested in what's actively used by power management daemons such as powerdevil or gnome-control-center. The new functionality may or may not be added in the future.
Yeah I mostly worry about both software suites using the same name and interface but then downstream software making assumptions on that.
Just want to avoid stepping on egg shells in the API design where possible.
Maybe it's best to advertise a compatibility level as well? I recall PPD has a version property. Maybe you can use "0.23" to indicate you match the API from 0.23 release?
Maybe it's best to advertise a compatibility level as well? I recall PPD has a version property. Maybe you can use "0.23" to indicate you match the API from 0.23 release?
Thanks, that's a nice suggestion, I added it into another open PR.
Can we please get this landed? Final Freeze is on Tuesday, and this needs to be in before then as things are listening on the UPower namespace exclusively already.
Can we please get this landed? Final Freeze is on Tuesday, and this needs to be in before then as things are listening on the UPower namespace exclusively already.
Thanks for the info, @zacikpa will backport it to Fedora today to land in Fedora on time.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-ceee3c1021 it seems stuck in testing.
What's holding this up to be merged? It's been shipped in Fedora for a while and it works fine.
It would be helpful to KDE to have this merged sooner rather than later (and also a new release with it made) because the upcoming Plasma 6.3 release needs this change to properly detect that tuned-ppd is installed.
The final release is on February 11th, so ideally it would be packaged and released in the various rolling release distros before then.
Thanks folks!
It would be helpful to KDE to have this merged sooner rather than later (and also a new release with it made) because the upcoming Plasma 6.3 release needs this change to properly detect that
tuned-ppdis installed.The final release is on February 11th, so ideally it would be packaged and released in the various rolling release distros before then.
Thanks folks!
Sorry for the delay, we initially planned TuneD upstream release to December, but I didn't make it. Due to other deadlines the stable version has to be released in January, which means RC version should happen during next week. The 11th February should be fine and it should also give some time to distro packagers.