panels/keyboard/cc-keyboard-panel.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 keyboard: allow disabling alternate characters key

Support for toggling a binding was added to accommodate the compose key.
At the time, I avoided changing the behavior of the alternate characters
key.

But it seems good to change this, which should resolve
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/918

meson.build | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 build: look for snapd-glib-2

panels/mouse/cc-mouse-caps-helper.c | 7 7 + 0 - 0 !
panels/mouse/cc-mouse-panel.c | 16 9 + 7 - 0 !
2 files changed, 16 insertions(+), 7 deletions(-)

 expose touchpad settings if synaptics is in use

Upstream is aggressively pushing for libinput over synaptics. However that
creates a factually incorrect situation where gnome-control-center thinks
there is no touchpad unless you're using the xserver-xorg-input-libinput.
This patch adds support for both drivers, removing the code that would
hide the touchpad settings when xserver-xorg-input-synaptics is in use.

This patch is only useful in the GNOME on Xorg session.
In GNOME on Wayland, libinput is used anyway.

This patch requires a companion patch in mutter which GNOME has rejected.

https://gitlab.gnome.org/GNOME/mutter/merge_requests/37

panels/user-accounts/cc-add-user-dialog.c | 6 4 + 2 - 0 !
1 file changed, 4 insertions(+), 2 deletions(-)

 debian's adduser doesn't allow uppercase letters by default.

tests/network/meson.build | 1 1 + 0 - 0 !
tests/network/test-network-panel.py | 3 2 + 1 - 0 !
2 files changed, 3 insertions(+), 1 deletion(-)

 ignore result of test-network-panel

This is a workaround for the test intermittently failing, especially
on slower architectures. Continue to run it with the result ignored,
and force its output to be logged, so that we can see how often it
fails in practice.

Bug: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1768

shell/cc-panel-loader.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 firmware-security: disable

Not yet useful enough to justify its inclusion by default here

You can get the same info by running
fwupdmgr security

If you drop this patch, add a Depends: fwupd [linux-any]

https://launchpad.net/bugs/1987162

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