Phillip released 4.5 which has some new functionallity, some clean up and
some bug fixes. It looks like he worked pretty hard on it for about
the last 6 months. I don't think that the new functionallity will break
any of our normal stuff, but if something breaks that uses it, that would
be a good possibility to check out.
The man pages are currently still out of date, but you can use the program's
help to get up to date documentation.
I had a successfull build after tonight's compose started, so the earliest
it will show up in rawhide is Saturday morning (in the US), assuming no one
off rawhide composes.
You can currently get a summary of changes at:
== Summary ==
We will install power-profiles-daemon in Fedora Workstation and enable
it by default. power-profiles-daemon allows the user to choose between
optimizing for system performance or battery life.
== Owner ==
* Name: [[User:Hadess| Bastien Nocera]]
* Email: bnocera(a)redhat.com
* Name: [[User:Catanzaro|Michael Catanzaro]]
* Email: mcatanzaro(a)redhat.com
* Name: [[User:Ngompa|Neal Gompa]]
* Email: ngompa13(a)gmail.com
== Detailed Description ==
From the upstream README:
power-profiles-daemon offers to modify system behaviour based upon
user-selected power profiles. There are 3 different power profiles, a
"balanced" default mode, a "power-saver" mode, as well as a
"performance" mode. The first 2 of those are available on every
system. The "performance" mode is only available on select systems and
is implemented by different "drivers" based on the system or systems
In addition to those 2 or 3 modes (depending on the system), "actions"
can be hooked up to change the behaviour of a particular device. For
example, this can be used to disable the fast-charging for some USB
devices when in power-saver mode.
GNOME's Settings and shell both include interfaces to select the
current mode, but they are also expected to adjust the behaviour of
the desktop depending on the mode, such as turning the screen off
after inaction more aggressively when in power-saver mode.
== Feedback ==
<!-- Summarize the feedback from the community and address why you
chose not to accept proposed alternatives. This section is optional
for all change proposals but is strongly suggested. Incorporating
feedback here as it is raised gives FESCo a clearer view of your
proposal and leaves a good record for the future. If you get no
feedback, that is useful to note in this section as well. For
innovative or possibly controversial ideas, consider collecting
feedback before you file the change proposal. -->
== Benefit to Fedora ==
Shipping power-profiles-daemon enables GNOME to display and offer
users the ability to adjust configuration related to power management
similar to other operating systems, which can improve the quality of
the on-battery experience (with respect to longevity of operating on
== Scope ==
* Proposal owners: Add Recommends: power-profiles-daemon to
gnome-control-center package. Add systemd preset to fedora-release.
* Other developers: N/A (not needed for this Change)
* Release engineering: N/A (not needed for this Change)
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: Nope.
== Upgrade/compatibility impact ==
power-profiles-daemon will be installed on upgrade to Fedora 35 if
gnome-control-center is installed. Since the default power profile is
the balanced mode, users should not notice performance changes (sans
bugs), but the option to manually select either performance or power
saving mode will now be present.
== How To Test ==
Visit the Power settings panel in gnome-control-center and switch
between performance, balanced, and power save mode. Look for
unexpected behavior changes over long periods of time. For example,
selecting Performance mode should improve system performance but
reduce battery life. Selecting power save mode should reduce
performance but increase battery life. Selecting balanced mode should
not change anything.
The selected power save mode should persist across system reboots.
== User Experience ==
GNOME Control Center will show a new section in the Power page giving
users the option to select power modes:
* Balanced (the default)
* Performance (to maximize performance)
* Power saver (to maximize battery life)
User selection of these profiles will set various tunables to meet the
needs as described in the profiles.
== Dependencies ==
gnome-control-center depends on power-profiles-daemon to offer power
saving options. If not installed, these options will not be present in
the power panel.
== Contingency Plan ==
* Contingency mechanism: we can easily remove the Recommends: in
gnome-control-center or the preset in fedora-release if necessary.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No
== Documentation ==
The only documentation is the upstream project README:
== Release Notes ==
Fedora Workstation now ships with power-profiles-daemon installed and enabled.
He / Him / His
Fedora Program Manager
I’d like to get python-xds-protos
(https://bugzilla.redhat.com/show_bug.cgi?id=1980041) reviewed so I can
update grpc to version 1.39.0 in Rawhide in time for Fedora 35.
This is a new dependency for grpc—a weirdly circular one that’s
ultimately generated from sources inside grpc, but is separately
versioned and separately distributed (generated sources only) on PyPI,
so I am treating it as a separate package.
I’m happy to review another package, or a handful of simple packages, in
exchange. I’m particularly accustomed to reviewing Python, C, C++,
review something else as long as reading the relevant domain-specific
packaging guidelines is enough to get me through the review.
A few years ago, I created release schedules through Fedora Linux
36. We've almost used up that buffer, so it's time to create the next
few years worth of schedules. Before I start that, I want to take the
opportunity to make sure the schedules match reality.
For teams that already have tasks on the release schedules, I have
opened issues in the schedule repo. Please use those to let me know
what changes make sense. You may also be hearing from members of the
Program Management team about those soon. If your team is not
represented on the release schedule but you think it would be, file a
For more information, check out my Community Blog post.
He / Him / His
Fedora Program Manager