~vcs-imports/gnome-control-center/+git/gnome-control-center:rhel/8.4.0

Last commit made on 2021-04-13
Get this branch:
git clone -b rhel/8.4.0 https://git.launchpad.net/~vcs-imports/gnome-control-center/+git/gnome-control-center

Branch merges

Branch information

Recent commits

1720aab... by Kalev Lember <email address hidden>

Update translations

https://bugzilla.redhat.com/show_bug.cgi?id=1876291

e7094cd... by Ray Strode <email address hidden>

printers-Update-entries.patch

972698d... by Carlos Garnacho

Update translations

1964217... by Carlos Garnacho

network: Handle Infiniband as a wired interface

The configuration/UI we expose for wired settings are meaningful for those
devices as well.

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

751cd4f... by Carlos Garnacho

network: Rename section header

The "Bluetooth" section is actually a catchall section for all
device types we don't know much specifically (Includes, but not
limited to Bluetooth).

Rename/relabel it to something more comprehensive.

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

383ffa8... by Carlos Garnacho

sound: Ensure to preserve sound theme when changing from default

The sound theme change itself triggers signals that are handled here
in the GSettings handlers, possibly resulting in it changing the
theme back to default. Ensure we are handling a real change here,
the sound theme will be updated through other means (eg. the row
changed handler).

c50ef0f... by ethan.hsieh

power: correct the value of 90 minutes to 5400

0d3213d... by Peter Hutterer

wacom: ignore the wacom driver's touch tool type

When the wacom driver handles the touch device, we get a tool id of 0x3. Let's
ignore that because we don't need a tool for the touch node.

Ideally we should be able to rely on the GDK tool type but that one is always
GDK_DEVICE_TOOL_TYPE_UNKNOWN see
https://gitlab.gnome.org/GNOME/gtk/merge_requests/453

A GTK bug (also fixed in that MR) prevents the tool id from updating.
Until that GTK bug is fixed the pen will only be detected if it is the first
event from this physical device. If the touch node sends an event before the
pen, the pen won't be detected.

6c99731... by Peter Hutterer

wacom: Map wacom-driver-specific generic IDs to 0

The xf86-input-wacom driver doesn't use 0 for tools that do not have an id or
serials. Serials default to 1, and the tool id is either 0x2 for stylus or 0xa
for eraser, see xf86WacomDefs.h, the defines for STYLUS_DEVICE_ID and
ERASER_DEVICE_ID.

libwacom uses 0xfffff and 0xffffe for the generic pens and all the lookup code
we have in the panel is designed for a serial/tool id of 0. So let's just map
the wacom driver IDs to 0 at the only transition point between Gdk and our
panel.

No devices with serials 0 or hw ids 2/10 exist, so this shouldn't have side
effects. This only affects X + xf86-input-wacom.

5201817... by Benjamin Berg <email address hidden>

user: Support devices with more than 5 enroll steps

We are currently adding support for Synaptics devices that require 8
steps. Add another row for images which brings us to up to 10
supportable steps for now.