gnome-shell:bilelmoussaoui/libcanberra-sound

Last commit made on 2022-04-14
Get this branch:
git clone -b bilelmoussaoui/libcanberra-sound https://git.launchpad.net/gnome-shell

Branch merges

Branch information

Name:
bilelmoussaoui/libcanberra-sound
Repository:
lp:gnome-shell

Recent commits

5961bf1... by Bilal Elmoussaoui <email address hidden>

sound player: Add Shell implementation of mutter#2375

ef74f92... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

background: Do not queue idle when cancelled

A cancelled cancellable means that the background was destroyed,
so we shouldn't queue an idle or emit the 'loaded' signal anymore.

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5337

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2268>

dd28832... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

background: Pass cancellable when querying file info

Otherwise it is possible that the operation completes successfully
after the background has been destroyed, which will throw a warning
(caused by accessing the this._fileWatches object after it has been
nulled).

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5337

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2268>

e69da36... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

layout: Make sure startup animation completes

We currently complete the animation using an onComplete handler,
which only runs if the corresponding transition was stopped when
finished.

While it is unexpected that the transition is interrupted, it can
apparently happen under some circumstances (like VMs with qlx).
The consequences of that are pretty bad, mainly due to the cover
pane that prevents input during the animation not getting removed.

Address this by always completing the animation when the transition
is stopped, regardless of whether it completed or not.

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5337

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2269>

436ebc2... by GunChleoc

Update Scottish Gaelic translation

824deaf... by Daniel Mustieles

Updated Spanish translation

5479479... by Yaron

Update Hebrew translation

7f4f328... by Simon McVittie

Specify API versions for all public GIR APIs, except GLib

If one of these libraries breaks its GIR API in future, then upgrading
packages unrelated to gnome-shell might pull in the newer version,
causing gnome-shell to crash when it gets a newer GIR API that is
incompatible with its expectations. For example, this seems to be
happening in Debian testing at the moment, when GNOME Shell 41.4
imports GWeather and can get version 4.0 instead of the version 3.0 that
it expected.

Adding explicit API versions at the time the newer version is released
is too late, because that will still let the newer version of the GIR API
break pre-existing GNOME Shell packages. Prevent similar crashes in
future by making the desired versions explicit.

This is done for all third-party libraries except GLib, similar to the
common practice in Python code; if GLib breaks API, then that will be
a disruptive change to the whole GLib/GObject ecosystem, regardless.

Gvc, Meta, Shell, Shew, St are not included because they're private
(only exist in a non-default search path entry).

Clutter and Cogl *are* included, because we need to import the fork of
them that comes with Meta, as opposed to their deprecated standalone
versions.

Signed-off-by: Simon McVittie <email address hidden>
Bug-Debian: https://bugs.debian.org/1008926
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2261>

0e3a1bd... by Jordi Mas

Update Catalan translation

58f3688... by Trần Ngọc Quân

Update Vietnamese translation