GNOME Settings has two Screen Blank controls and only one of them works.

[Knickers Brown]

GNOME Settings has two Screen Blank controls and only one of them works.

Expected

Screen Blank controls should preserve the values you set them to.

Actual

One of the two Screen blank controls does not preserve the value that you set it to.

Version Info
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Kinetic Kudu (development branch)
Release: 22.10
Codename: kinetic

$ gnome-control-center --version
gnome-control-center 43.beta

$ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
1:43~beta-1ubuntu2

Reproducing

1. Run gnome-control-center power
2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a different value.
3. Change to another panel (tab) and change back to Power. (e.g. change to Audio then back to Power)
4. Observe that your Screen Blank setting has reverted to the prior value (e.g. if you set it to "never" it will return to 5 minutes).
5. Change to the Privacy panel, then to the Screen panel.
6. Change the setting for Blank Screen Display to a different value.
7. Change to another panel and then back to Privacy->Screen.
8. Your change to the value of Blank Screen Display will have been retained (will be the same as you set it a moment ago).
9. Change to the Power panel and the Screen Blank setting that you selected will be displayed there too.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 29 15:14:39 2022
InstallationDate: Installed on 2022-08-29 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

[Knickers Brown (metta-crawler)]

Upstream bug report
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2025

Upstream commit that fixes this:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/37f5cbe6af5ea71221309669f8b02d5e423956e7

[Knickers Brown (metta-crawler)]

This is no longer true:
no longer affects: gnome-control-center (Debian)

Which is to say this does affect Debian (bookworm/sid) "unstable".

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

The issue is fixed in git upstream now, https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/37f5cbe6a and the change will be in the next update before 22.10

[Knickers Brown (metta-crawler)]

GNOME 43.rc is scheduled to be released on Sept 3, 2022 and should come with the fix for this.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-control-center - 1:43~rc-1ubuntu1

---------------
gnome-control-center (1:43~rc-1ubuntu1) kinetic; urgency=medium

  * Merge with Debian
  * Refresh patches

gnome-control-center (1:43~rc-2) unstable; urgency=medium

  * New upstream release
    - Fixes Screen Blank control (Closes: #1018672, LP: #1988087)
  * debian/control.in: Bump minimum meson to 0.57.0
  * Build against libsoup3 libraries
  * Drop sound patch: applied in new release

gnome-control-center (1:43~beta-4) unstable; urgency=medium

  * Cherry-pick patch to fix sound alert selection (LP: #1987161)
  * Recommend gnome-bluetooth-sendto

gnome-control-center (1:43~beta-3) unstable; urgency=medium

  * Add patch to disable new Device Security panel.
    It's too technical and unhelpful currently (LP: #1987162)
    You can get the same info by running
      fwupdmgr security
  * debian/control.in: Depend on webp-pixbuf-loader
    - This is required to display several of the new GNOME 43
      wallpapers. Please log out and log back in for this feature
      to work fully.

 -- Jeremy Bicha <email address hidden> Tue, 06 Sep 2022 09:25:05 -0400