`adw_combo_row_get_selected_item()` does not transfer ownership, so we
shouldn't attempt to free the returned item. Otherwise use-after-free
can occur.

Fixes #3240


(cherry picked from commit 38a84d07)

Using `g_autoptr()` for multiple variables on the same line is awkward,
and in this case, also incomplete as we need to free the full GList.

Also, fix a GtkExpression leak, as setting it on a combo row does not
take ownership.


(cherry picked from commit 62feddf7)

- Remove the top margin from the "Turn off Airplane
Mode", as this is already handled by libadwaita
- Fix all status pages not being vertically centralized


(cherry picked from commit cf75db86)

Otherwise we're missing translations in the AdwAboutWindow.

Commit d9970d4f fixed this (by accident?) already for GNOME 47.

Apply part of that commit to fix it for GNOME 46 too.

See #3252

The "Add Printer..." button label is already self
explanatory. Also, "All Connected and Network
Printers" seems like a misplaced tooltip, as
the dialog is about adding a printer, not showing
connected printers.

Closes https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3267


(cherry picked from commit dd32ddff)

Colord profiles have to be "connected" for most operations on them.
Turns out that by default, the currently active profile is always
connected, but others aren't. So we get criticals setting such a
profile system-wide.

So, make sure a profile is connected before setting it system-wide.

(cherry picked from commit 7de79a5b)

Otherwise we also cannot test them for equality.

Closes #3264

(cherry picked from commit c96d4534)

By doing that, the predefined avatars are distinct for a11y purposes.


(cherry picked from commit 0eeaabb1)

Fixes wrong GPU names when g-c-c is launched using dGPU

(cherry picked from commit 2b111f06)

Volume-level source streams without a name were causing the Sound panel
to crash.

Let's make sure we only expose streams with a non-NULL name.

Fixes #3197


(cherry picked from commit 542419d9)

(cherry picked from commit 4a4c58f9)

See https://handbook.gnome.org/maintainers/making-a-release.html

(cherry picked from commit 490adea2f5dcb68b1c33a2e9b61bf469a6d9a07f)

(cherry picked from commit eca398728875086d218b1d40b5817514189eb344)

We have now a release-build job for "dist".

(cherry picked from commit 37b5b6de90157fb2211d95a88c63cf2c7ecbf5ad)

"release-service-sandbox" was for testing.

(cherry picked from commit 54526a029176c1c694442265588ce0414b05c9bd)

(cherry picked from commit 91fa1846)

In the past it was a slightly transparent black dialog that was resized
according to the calibrated monitor, but resizing doesn't let us control
the positioning, meaning we can only fullscreening. Prepare for that by
making it a regular GtkWindow (dialogs are deprecated anyway), and add
our custom CSS to make it black with grey buttons, as it was before,
only now fully opaque.

(cherry picked from commit 2e41b808)

Closes: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/948
(cherry picked from commit 06168bf8)

The calibration state is reset, but the second time the assistant is
run, the tree view signalling isn't hit, meaning the values selected up
front isn't forwarded to the calibration. The assistant page was also
still marked as "completed" even though no state had been set.

What this meant is that even though e.g. the device kind was appearing
to be selected to something, the actual calibration state was still the
default (unknown), which would later hit a soft assert and a error null
pointer dereference.

Fix this by resetting the assistant pages' completeness to incomplete,
and run the same code path for when the tree view options were selected
when an assistant page is prepared.

Closes: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1196
(cherry picked from commit d0a550b2)

Update to upstream version '46.7'
with Debian dir 20e25a8ceda9e1cd2d96b8333a4dd727668dae63