[Slackbuilds-users] Bluefish and glib2

[Didier Spaier]

On 30/04/2025 18:02, Willy Sudiarto Raharjo wrote:
> This is just one of the example
> GLib 2.83.0, 2024-11-06
> Rename multiple g_unix_mount_*() APIs to g_unix_mount_entry_*()
> Update to Unicode 16.0.0; there may be bugs in linebreaking support
> 
> If the program is a toolchain, it's probably easier to create a new *-opt script
> which is newer than what we have in Slackware, like meson, setuptools, rust,
> etc. If it's library, we might end up with same situation when some scripts in
> SBo requires newer glib2/icu4c version in the future while the rest is not yet
> patched to support the newer version.

I just came across such a case:
Running "flatpak install gedit" after having confirmed every tile flatpak
installs a dep I get in the terminal these messages if glib2-2.84.1 is installed
/
(flatpak install:21726): GLib-GIO-CRITICAL **: 15:53:58.926: GFileInfo created
without standard::size
(flatpak install:21726): GLib-GIO-CRITICAL **: 15:53:58.926: file
../gio/gfileinfo.c: line 1860 (g_file_info_get_size): should not be reached

This does not seem to hurt in this specific case as gedit is installed and work
but...

On the other hand if I type:
upgradepkg glib2-2.70.3-x86_64-1.txz
After that no more messages using flatpak, but applications like geany or
mate-terminal fail to start with an error message like:
geany: symbol lookup error: /usr/lib64/libatk-1.0.so.0: undefined symbol:
g_once_init_enter_pointer
mate-terminal: symbol lookup error: /usr/lib64/libatk-1.0.so.0: undefined
symbol: g_once_init_enter_pointer

These are only a few examples that are a lot of other issues, like firefox not
starting or crashing.

FYI /usr/lib64/libatk-1.0.so.0 is shipped in at-spi2-core-2.56.2-x86_64-slint

If I try to rebuild at-spi2-core against glib2-2.70.3 I
get:../atk/meson.build:140:18: ERROR: Dependency lookup for
gobject-introspection-1.0 with method 'pkgconfig' failed: Could not generate
cflags for gobject-introspection-1.0:
Package 'gobject-introspection-1.0' requires 'glib-2.0 >= 2.82.0' but version of
glib-2.0 is 2.70.3

For Slint at-spi2-core is an important piece of the accessibility stack, meaning
that if I can't keep all these pieces updated I will have to downgrade the orca
screen reader from 48 to 41.3 (the version currently maintained by Bob Funk @
SBo) which would not make happy Slint users relying on it...

So for now I will install back glib2-2.84.1, crossing fingers that this does not
trigger more severe issues than the one with flatpak.

Clues to find out which packages won't work with a "too new" or "too old" glib2
appreciated, ldd not giving a clue in this case, it seems. Maybe I do not user
it properly or there is another way to find out?

Thanks for having read this long rant.

Cheers,
Didier