Enhanced Open (OWE) is not being saved properly from connection-editor.
When we create a Wi-Fi connection using Enhanced Open (OWE) Security
from nm-connection-editor and save it, it was not being saved and the
security was being set as "None", with Wireless Security Setting
being discarded. This is fixed by this commit. The fix is also being
done in libnma (implementing OWE in libnma,
https://gitlab.gnome.org/GNOME/libnma/-/issues/9), but this commit
fixes meanwhile it gets ready.

It was solved by adding treatment for the case in which owe was set.
OWE is not treated anymore in the same case as None.

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

sound: clear the value on level_bar when stream is empty

We met an Input Device level_bar display issue on a machine which has
no internal mic. At first there is no external mic plugged, so the
Input Device list is empty and level_bar is gray color, after we plug
an external mic, the level_bar has red color ripples, then we unplug
the external mic, the Input Device list changes to empty and we
expect the level_bar changes back to gray color, but some bars are
still red color.

Here clear the self->value to 0 if the stream is empty, then the
level_bar will change back to gray color when Input/Output device
list is empty.

Signed-off-by: Hui Wang <hui.wang@canonical.com>

Mutter also installs keybindings but to the GCC share folder.
We need to read these as well as the keybindings in the BCC
share folder. Closes #3

https://gitlab.gnome.org/GNOME/gnome-control-center/issues/381
In short, these only kind of work for sandboxed apps
and its questionable whether they work here either.  Ubuntu
has disabled these.
So we'll inherit this patch to equally prevent confusion what
these options are for.

We moved the lock controls to the more logical displays in
and earlier commit.  This commit ensures the signals for the
lock controls point to the displays panel to ensure the
signals are created and function correctly.

Avoids clobbering certain custom settings that can't be set in UI.

Origin: https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/910
Bug-Ubuntu: https://launchpad.net/bugs/1934761

Meant to address issues mentioned in
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1214
using the solution proposed there.

There is no "None" option for the compose key, since there doesn't
appear to be a way to disable it on the unusual layouts where it's
available by default.

XKB options are a mess, but this seems like a more accurate
representation of how they function.

Origin: https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/910
Bug-Ubuntu: https://launchpad.net/bugs/1867548
Bug-GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/918

Origin: https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/910
Bug-Ubuntu: https://launchpad.net/bugs/1867548
Bug-GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/918

snap-store is a universal package installer.
Some budgie-distros do not ship with gnome-software.
Normally clicking an application allows users to open the
application in gnome-software.
With this patch, if snap-store is installed (and gnome-software
is not installed) then the application can be optionally opened
in snap-store.
If both gnome-software and snap-store are not installed then
the "open in software" button remains unavailable.
.
Patch taken from Ubuntu's G-C-C patching; its applicable to
all budgie distros.

This commit leverages the Ubuntu gnome-control-center patch
to enable an option to allow > 100% volume.  Stripped from this
patch is the restriction to only show for the Ubuntu desktop.
References to 'ubuntu' have been switched to 'budgie'.

Fixes: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/401
Bug-Ubuntu: https://bugs.launchpad.net/gnome-control-center/+bug/1862553

Lock screen notifications are not applicable with budgie-screensaver
Do not disturb is handled by raven, not here.

Dynamic workspaces do not work under budgie.  Lets hide this
from the UI rather than just deleting the code - this allows
easier reinstatement if we subsequently want to reimplement this
in budgie.
Separately, limit the number of workspaces to budgie's 8 otherwise
we get window manager crashes

Since this project uses git submodules, for distros
that build from tarballs - the tarball must contain the
source for this subprojects i.e. they cannot use a git tag.
Thus we need to publish formally a release containing
signed tarballs.

Requires BuddiesOfBudgie/budgie-desktop#6270dafa4f0dcfa508998d0f109e948834eaf152

This ensures the option isn't exposed on operating systems which do not carry Mutter X11 xrandr fractional scaling patches. The only operating systems that do are Manjaro and Ubuntu.

When this mode is selected we need to assume that all the monitors are scaled
by their scaling and the global UI scale.

Origin: https://gitlab.gnome.org/3v1n0/gnome-control-center/commits/layout-global-scale
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1820850
Forwarded: No, MPs will follow shortly

https://salsa.debian.org/gnome-team/gnome-control-center/-/raw/ubuntu/master/debian/patches/ubuntu/display-Support-UI-scaled-logical-monitor-mode.patch

https://salsa.debian.org/gnome-team/gnome-control-center/-/raw/ubuntu/master/debian/patches/ubuntu/display-Allow-fractional-scaling-to-be-enabled.patch

gresources and their calls from c module files have to match
where they don't we get either blank panels or segfaults
This revert changes everything back to gnome - its no harm leaving
at a value of gnome since resource files are not installed into
locations conflicting with gnome-control-center

Distro's can use LOGO="vendorname" in their /etc/os-release file.
If this is not specified then "budgie-logo" is assumed for the LOGO name prefix.

The chosen icon can be suffixed with "-flavor" for distros that are flavors of an overarching distro.
Two icons can optionally be specified - one for a dark panel; a dark panel logo should be suffixed with "-dark".
If no icon is found then the default budgie-desktop icon installed by
budgie-control-center is chosen.

Examples of a themed icon name:
mydistro
mydistro-dark
mydistro-flavor
mydistro-flavor-dark
budgie-logo-flavor
budgie-logo-flavor-dark
budgie-logo
budgie-logo-dark