(cherry picked from commit 6868a4a102902834f6c193b3a321053e2b82afb0)

(cherry picked from commit d058db6a091326962562a816169e345a50034217)

The others are not erroring out correctly for close_range syscalls,
causing issues when spawning. So use the "crun" runners and disable
"asan" as there is no overlap.

Some versions of mutter were not setting the use as active when the lid
was opened. Skip the test in case the current mutter version does not
contain the (latest) fix. This will also disable the test for older
versions that work, but that is fine.

Ignored in meson < 0.60.0, deprecated since 0.60.1 and fatal since 0.61.0.

Use the new GWeather major version.

The only change consists in replacing GWeatherTimezone with GTimeZone.

Despite the debounce logic introduced in
60621b90, GSD kept warning me of the
battery level every time my Logitech K600 keyboard (via Unifying
receiver) disconnects/reconnects.

Added another condition: when battery level drops to
`UP_DEVICE_LEVEL_NONE`, the previous entry in the hash table would not
be overwritten. This avoids duplicated warnings when transitioning
NONE->LOW->NONE->LOW.

Those usually get port names from UCM. Add common port names from
there.

The lid-switch is inhibited at startup, and a number of tests rely on
this inhibition to have been released again. Unfortunately, it seems
that sometimes we were not clearing all messages properly. Either way,
explicitly waiting for the uninhibit that happens at startup is sane.

Otherwise there is a race condition that can cause the FD to be closed
twice. Avoid this by signalling EOF through a separate variable and
always closing the FD from the main thread.

gnome-shell itself now handles the screenshot keys. This is required to
easily provide same-frame response to pressing a screenshot key.

gnome-shell itself now handles the screencast key too.

Right now, gsd-keyboard and gsd-xsettings have a strange relation
where the first sets the gtk-im-module dconf setting for the latter
to read the setting and forward it through XSettings.

Since this detection is highly X11 specific, make it happen in the
Xsettings daemon itself, from the relevant setting and device presence.

This makes users still able to shoot themselves in the foot by changing
the setting, X11 clients able to be told to switch to ibus if it turns
out necessary, and Wayland clients unaffected otherwise.

Related: https://gitlab.gnome.org/GNOME/gtk/-/issues/4443

Settings now directly uses systemd for managing the gnome-remote-desktop
service, thus we don't need to have gsd-sharing do it for us anymore.

Update to upstream version '42~rc'
with Debian dir e96dd2d2f4eece769f409dd13db704c300cba2a2

since it needs gnome-control-center 42 first

Gbp-Dch: Full

releasing package gnome-settings-daemon version 42~rc-1