Currently, every Flathub app is show as using a "legacy display manager"
whether they use x11 with --socket=x11, or wayland with
--socket=wayland and --socket=fallback-x11.
However, the fallback-x11 enables X11 only if the host doesn't support
anything else than x11, so strictly speaking, it's the host that uses
x11 and not usually the app.
So this commit stops from showing this warning if using x11 as fallback.
8a847bd...
by
Philip Withnall <email address hidden>
flatpak: Operate on a copy of the FlatpakInstallation
This means that global state changes, such as to the `no-interaction` flag
of the `FlatpakInstallation`, don’t escape outside the context of the
transaction currently being run.
This is a follow up to !283, using a suggestion by Matthias Clasen.
Signed-off-by: Philip Withnall <email address hidden>
bf68bb6...
by
Alexander Mikhaylenko <email address hidden>
Revert "trivial: Fix the padding in the new hamburger menu"
That commit added extra padding in the primary menu that no other app has,
remove it.
This reverts commit 26c02f458ab2b3b495ce2134c525e1a24d1d46d0.
8f07e75...
by
Matthew Leeds <email address hidden>
flatpak: Properly check if an app is a runtime
In gs_flatpak_set_kind_from_flatpak(), we use AS_APP_KIND_LOCALIZATION
and AS_APP_KIND_GENERIC in addition to AS_APP_KIND_RUNTIME, all for
things which from Flatpak's perspective are runtimes (their ref starts
with "runtime/"). So change checks in a few places to correctly identify
Flatpak runtimes instead of checking for AS_APP_KIND_RUNTIME, which has
the effect of ensuring that applications properly show as needing an
update when their locale extension needs an update, e.g. because the
user chose a language other than the one the locale extensions already
have.
