Thank you for your bug report. Could you provide some details on how you
set a profile which isn't available?
I'm a bit unclear also that it's a fix important enough to justify a
backport upload by itself, that's not an issue that users hit in normal
conditions.
The fact that we didn't see reports about it until now is also an
indication that it's not a common problem
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2037503
Title:
[jammy]backport #1453 from upstream
Status in gnome-control-center package in Ubuntu:
Incomplete
Status in gnome-control-center package in Debian:
New
Bug description:
In some cases, it was possible for a profile to be set (directly, or
through a hold) even though it wasn't supported. Don't assert in those
cases.
The bug in question makes the gnome-control-center crash if an unsupported
power profile is set using, say, powerprofilesctl.
Should be trivial to cherry-pick without breaking other components.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453
I had to wait for this long because I expected a 42.x backport in the
backports repository of .1 release, but no one bothered to do such a
backport.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
