GitLab

Update the UI after setting the effect priority and after undo/redo of
effects reordering.

Fixes #2178
Fixes #2234

The pipeline was being declared dead first when an error was reported on
the bus, and second when the async-done was not being received.

Fixes #2232

Should have been part of f4554628 and 13e7066b

Should have been part of f4554628

According to
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-launchable
it's "desktop-id", not "desktop".

Fixes #2140

Fixes #1171

To enhance performance while removing assets we are pausing
the previewer generation while deleting clips, this means that
the current previewer is always reset to None (in the Manager) and we
call `start_next_previewer` when we are done with the clip removal.
If the clip holding the generator that was being used before pausing
was not removed, it leads to that generator being restarted, but
previous code was just recreating a new pipeline from it, without
ever stoping previous pipeline, this previous pipeline was destructed
while in PAUSED... leading to the deadlock described in the bug report.

The strategy is to inform previewers that they should be
PAUSED so that they just restart when needed.

Fixes #2227

And document it

So that we can apply our knowledge of asset relocation when dealing
with deleted proxies and GES is finding the new asset location by
itself (after the user provided a specified a relocated asset).

This also requires:
    http://cgit.freedesktop.org/gstreamer/gst-editing-services/commit/?id=5f5cbd111cd41e11d3e2f875ed4545eb7c0e3df2

Fixes #2203

Updating the images daily

Minus a few remaining one in outdated string translation that should
probably just be removed.

Fixes #2226

Do not redefine a thing which was always defined in the included header,
since that breaks when upstream changes how they do things.

This is a holdover from the initial python2 version, since pycairo
dropped the use of downstream definition of Pycairo_CAPI during the
python3 port: https://github.com/pygobject/pycairo/commit/727470e8a170bf355c9689826bb1db95f7c1389e

See https://github.com/pygobject/pycairo/commit/921541295439f812ac51a6cc6d8143a8f10814b4
for the upstream change that broke this misuse.

The bould-tag (<b>) was was not closed (</b>) in the German translation
of the message string with the msgid starting with:
"Pitivi detected a serious backend problem ..."
And thus the text could not be set for the error-dialog.

This commit adds the closing-bould-tag and fixes
#2224

For example:
flatpak update --user org.gnome.Platform 3.28
Updating in user:
org.gnome.Platform/x86_64/3.28                       flathub 4afe5ccb6990
org.gnome.Platform.Locale/x86_64/3.28                flathub 1d96abcdc97b
Is this ok [y/n]:

This reverts commit 41dc6f4d.

The build option were changed only in the GStreamer 1.15 cycle.

Using Gst.debug_print_stack_trace()

For example:
flatpak install --user flathub org.gnome.Platform.Locale 3.24 --reinstall
Installing in user:
org.gnome.Platform.Locale/x86_64/3.24 flathub fabbccbd2dae
Is this ok [y/n]:

flatpak info returns an error if there are multiple versions of the
subpackage installed, requiring one of them to be specified.

Update the flatpak version check as we now require 0.10. Also cleanup
the way we check Sdk version.

Not simply using fatal-criticals as some criticals are outside of
control on the CI server (no dbus running there)

It requires patches in GES 1.14.2, we will bump the dep when released.

And fix all tests.

Fixes #2207