python-dbusmock will also stop importing all session services that are
installed on the host system by default (as is already the case for
system services). With this change, the dconf service cannot be
activated anymore unless we explicitly enable the service in the
environment.

Add the appropriate call to enable the service, guarded by a check that
the method exists to be compatible with older dbusmock versions.

See: https://github.com/martinpitt/python-dbusmock/pull/108

This is broken comparing with stable release numbers, like 42.0. This
version is also released, so it sounds better to simply depend on that.

This setting used to be modified by gsd-keyboard at runtime, but it no
longer does. We want to leave this setting in a pristine state before
we lend control to the user in order to avoid setting leftovers make
GTK and others use the unintended IM module.

Since the setting is actually staying on the same schema/path, there is
no nice mechanism that would help us in doing a one-time port, so rely
on a file at ~/.cache to make this happen once. In the common case, it
just adds one stat() more at startup.

After this migration is done, the gtk-im-module setting can be considered
in full control of the user.

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.

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: gtk#4443

gnome-shell itself now handles the screencast key too.

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

Benjamin Berg authored Feb 10, 2022 and Benjamin Berg committed Feb 10, 2022

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.

Benjamin Berg authored Feb 10, 2022 and Benjamin Berg committed Feb 10, 2022

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.

Guido Günther authored Sep 23, 2021 and Benjamin Berg committed Feb 10, 2022

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

Marti Raudsepp authored Oct 21, 2021 and Benjamin Berg committed Feb 10, 2022

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.

Emmanuele Bassi authored Dec 31, 2021 and Benjamin Berg committed Feb 10, 2022

Use the new GWeather major version.

The only change consists in replacing GWeatherTimezone with GTimeZone.

Marvin Schmidt authored Jan 26, 2022 and Benjamin Berg committed Feb 10, 2022

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

Benjamin Berg authored Feb 10, 2022 and Benjamin Berg committed Feb 10, 2022

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.

Benjamin Berg authored Feb 07, 2022 and Benjamin Berg committed Feb 10, 2022

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.

sicklylife authored Feb 10, 2022 and Administrator committed Feb 10, 2022

(cherry picked from commit d058db6a)

sicklylife authored Feb 10, 2022 and Administrator committed Feb 10, 2022

(cherry picked from commit 6868a4a1)

 We now have a boolean setting that determines whether the high-contrast
theme should be used. Support it by automatically setting the existing
`gtk-theme-name` and `gtk-icon-theme-name` properties when enabled.

With that, it is no longer necessary to change the regular theme settings
for high-contrast, so toggling between high-contrast and a non-default
theme finally works reliably.