Will this Settings (GNOME Control Center) bug fix ever get into 22.04?

Support and Help
1

Ubuntu Version:
22.04

Desktop Environment (if applicable):
GNOME

Problem Description:
When the CPU scaling governor is set to “performance” (this is done via a startup script) the GNOME Settings app fails when you switch to the Power tab (see error message below).

After this has happened, you can’t successfully run Settings again until you reset the current panel:

gsettings reset org.gnome.ControlCenter last-panel

This is a pretty annoying problem for users who don’t know how to do this gsettings fix. The Settings app should always be available.

I believe this issue has been fixed two years ago in GNOME, see this issue:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1504

My question is: will this fix ever make it into Ubuntu 22.04? Is there some process through which I can request that this is fixed in 22.04?

Screenshots or Error Messages:

(gnome-control-center:13779): cc-power-profile-row-CRITICAL **: 11:02:13.689: cc_power_profile_row_get_radio_button: assertion 'CC_IS_POWER_PROFILE_ROW (self)' failed
**
power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button)
Bail out! power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button)
Aborted (core dumped)
2

Hello! I have seen this issue on my laptop too.

It might, if there is a bug tracking the issue in LaunchPad. I had a look, and couldn’t see one. If you run ubuntu-bug gnome-control-center then it should walk you through filing a bug, which you can link to the upstream bug.

3

Hi, and welcome to Discourse. It is called a “Stable Release Updates”, and the process is described here:
https://canonical-sru-docs.readthedocs-hosted.com/en/latest/reference/requirements/

4

This bug has only been fixed in GNOME 43 while 22.04 ships with GNOME 42.x …

While Ubuntu does do include point releases for GNOME particularly (unlike for other packages that only get backported security fixes), it will not include new major versions (like the one going from GNOME 42 to 43), so the answer is no, unless someone in GNOME does this and ports it into a point release …

Your best bet is to move to 24.04 to get this fix

EDIT: what @popey said is also true, you can indeed always file a bug in launchpad and hope someone backports that particular fix, but AFAIK performance is not handled at all by the UI anymore so it might be treated with very low priority because the breakage can only happen when you do something non-standard via tweaking the underlying system…

StableReleaseUpdates usually do not happen for single parts of GNOME

1 Like
5

Hi all, many thanks for the prompt and useful replies, much appreciated!

To answer some of the points raised:

  • I’ll look into the Stable Release Updates process
  • we will be staying on 22.04 until close to the end of its support time, because a) we want to keep our base platform as stable as possible and b) we reply on some third party hardware drivers which currently only support 22.04
  • a different topic, but I don’t understand why “performance” is not a properly supported CPU governor in the GNOME UI. In our case we want performance mode because we prioritise consistent CPU performance over energy saving
6

You will have to check with the GNOME upstream developers on this one, they usually do not take such decisions without discussion, so there is probably a documented reason for this …