This works around a relayout loop that makes the Debian installer hang.
To minimize the effect on installed systems, this is
`#ifdef DEBIAN_INSTALLER`; we currently have no evidence of similar
relayout loops outside the d-i environment.
Closes: #988786
This is not a hard dependency, but should be installed in nearly all
cases. Increasingly many icons are provided in SVG format, so
applications will appear broken if the SVG pixbuf loader is not
installed. See #980396 for more information.
adwaita-icon-theme already Recommends librsvg2-common, but people who
routinely do not install recommended packages will get a better hint
about how much will be broken by its removal if GTK also recommends it.
These symbols are all canonically provided by GObject, part of the
libglib2.0-0 package, on which GTK depends. They were accidentally
included in the GTK 2.24.32 ABI, but if they are removed, dependent
programs will find the copies in GObject, which are completely
compatible (it has the same content and was generated by the same
script).
gtkmarshal.c in GTK 2.24.32 was generated by a version of
glib-genmarshal that produced unintended symbols. It was regenerated
for 2.24.33, but it looks as though a few packages might already be
referring to those symbols. Patch them back in for ABI compatibility.
- Windows-, macOS- and CI-specific changes not included here
- Update metadata for #895043 patch, applied upstream
- Add a new patch to fix a GIMP segfault after switching themes
- Add a new patch for a build fix
It turns out that we do not need to have separate command lines for
running the Visual Studio preprocessor for 32-bit builds and 64-bit
builds as `_WIN64` is automatically defined by the 64-bit compilers.
This means that we can clean up the project files a bit.
GTK2 uses different gtk.def files on 32-bit and 64-bit Windows. GTK2
source tarballs ship pre-generated gtk.def for 32-bit Windows. If the
user wants to build for 64-bit Windows, the pre-generated gtk.def must
be deleted before the build to force regeneration, or it will fail to
link with 'symbol not defined' errors because the 32-bit Windows build
includes more legacy functions than the 64-bit Windows build.
While users who want to build for 64-bit Windows can delete gtk.def in
the build script, which is currently what most build scripts do, doing
so breaks out-of-source build. On AUR, MinGW packages are usually built
and packaged in the following order:
1. Run 'configure' and 'make' to build for i686-w64-mingw32.
2. Run 'configure' and 'make' to build for x86_64-w64-mingw32.
3. Run 'make install' for i686-w64-mingw32.
4. Run 'make install' for x86_64-w64-mingw32.
It fails because step 3 sees gtk.def left by step 2, which is generated
for a different build. In step 3, make sees the gtk.def change and runs
libtool to relink libgtk-win32-2.0-0.dll. libtool fails to find a lot of
necessary libraries, decides that it is not possible to build a DLL with
-no-undefined, and produces only the static library. It then tries to
relink executables with the static library, and fails with undefined
reference to 'IID_IUnknown' because -Wl,--start-group isn't used and
the use of -Wl,-luuid prevents libtool from using the correct order.
To resolve the problem, move gtk.def to builddir so different builds can
have different gtk.def files while sharing the same source tree. This
also means that the source tarball will no longer include pre-generated
gtk.def file, which should be acceptable because it is already broken on
64-bit Windows.
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3029
This is mainly to be nice to pkgconf. The versioned dependency was there
to ensure multiarch support, and both pkgconf and pkg-config had multiarch
support in oldstable.
Closes: #734480
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/2684
GIMP segfaults while switching themes between dark and gray and inputting Ctrl-O
to open a file. This is because p advances past end of pixbuf in pixbuf-render.c
compute_hint() with num_channels = 3 (no alpha). This is resolved by fixing the
if statement to only check for alpha, thereby advancing p, if there is an alpha
channel.
In the Vietnamese Quoted-Readable input method, punctuation following a
base letter is converted into diacritical marks, for example a( → ă.
(See <https://en.wikipedia.org/wiki/Vietnamese_Quoted-Readable>.)
A 2008 bug report in Ubuntu argued that this is a problematic default,
particularly when typing passwords, where the effect of the punctuation
is non-obvious.
According to the bug reporter, VIQR is popular with Vietnamese users
living elsewhere in the world, where Vietnamese keyboards are unlikely
to be readily available, but is not a popular choice within Vietnam,
where the Telex or VNI input modes are preferred.
Closes: #183
Bug-Debian: https://bugs.debian.org/895043
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/191451
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
