"libadwaita"'s xref is actually a pointer to libadwaita.so in
gnome-themes-extra. As a result of this, the library from
gnome-themes-extra gets referenced instead of the actual package.
Fix this by using 'libadwaita1' instead, like other packages that use
libadwaita.
it.
This should make the different URLs we had previously consistent with
one another, and ease maintenance burden.
This is only temporary though since eventually gi-docgen will become
part of the book, when Pierre's python-modules branch is brought into
trunk.
instead of --buildtype=release to work around a crash in gnome-shell.
Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5512
If close an focused app window via the Activities overview, an assertion
fail will be triggered in clutter_actor_get_preferred_{width,height}.
When debug is disabled, the assertions are disabled as well and the
issue turns into a NULL dereference, leading to a crash.
This is definitely not a proper fix. But the issue has been haunting
gnome-42 and 43, and the upstream has not given any response yet.
Note that it's not a "compiler misoptimization" issue. The assertion
fails even with -O0, i. e. if both the assertions and compiler
optimization are disabled, gnome-shell will crash as well.
And it fails to build if libsoup3 is not installed unless
"-Dsoup3=false" is passed to meson (I do not want to put this in
command explanations. We should use soup3 as much as possible).
This is useful for users who don't want a display manager, as well as
users who have the proprietary NVIDIA driver installed and want Wayland
support (since GDM won't show the session).
I placed this in the GDM page since GDM is still required for such a
session to work anyway (the .GIR files in particular), but I'm open to
moving it in the future if desired.
The release tarball contains generated man pages since gnome-shell-40 so
asciidoc is not a dependency unless you'll build gnome-shell from git
snapshot. And, the option has been renamed to "extensions_tool" and we
don't have any strong reason to use it now.
Update to gjs-1.72.1
Update to tracker3-3.3.2
Update to gnome-bluetooth-42.2
Update to epiphany-42.3
Update to libadwaita-1.1.3
Update to libhandy-1.6.3
Update to gnome-desktop-42.3
ffmpeg won't be used if gst-plugins-base is installed.
The upstream installs gst-plugins-good and gst-libav for the CI, so keep
them as recommended but runtime. gst-plugins-bad and ugly are not
mentioned at all.
Both packages handle libsoup2 and libsoup3 as follows: if one libsoup is
already loaded by the process, it will use the loaded one. Otherwise,
try to load libsoup3 first, and if it's not found try libsoup2.
But they need the headers of one libsoup version at build time to
support loading this version at runtime, so we can't make the libsoups
runtime dependency.
For tracker 3, also demote libsoup2 to recommended. It can be built with
libsoup3 only (and the building system will do it silently if libsoup3
is installed but libsoup2 not). But I'm not sure if it will cause
runtime issues.
libsoup3 should be OK now. There have not been any issues discovered
as of the date of this commit.
gvfs is also changed to add back http. Also avahi is now recommended.
avahi can be removed by adding -Ddnssd=false but that requires a patch.
https://gitlab.gnome.org/GNOME/gvfs/-/issues/621
This has been fixed upstream.
The maintainer did not pay enough attention using "make dist" to
generate the release tarball. See:
https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/109
bdubbs has partially worked around the issue, but on systemd we still
get:
make[2]: *** No rule to make target
'daemon/gnome-keyring-daemon.socket', needed by 'all-am'. Stop.
Instead of fetching this .socket file separately, it's easier to just
download a clean tarball and regenrate the configure script ourselves.
I'd prefer them to switch to meson and avoid this kind of problem
forever.
