New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/39393#issuecomment-1253262508

Comment:
Edit: regarding the glib issue, here is a more explanation for it: (it's a null ptr dereference)
https://gitlab.gnome.org/GNOME/gimp/-/issues/8576

> nor did they mention the failure in gimp

Maybe he didn't see it? Or maybe he didn't want to comment on it due to lack of information. There's bug report for it on the gimp gitlab so hopefully someone can figure out where the issue is coming from and if it should be fixed in gimp or glib.

> for them issue/bug or any change that causes errors, it is a feature

I don't see anything wrong with what ebassi said.
Sometimes applications need to be updated to fix issues with improper/deprecated usage of their libraries, this isn't a gnome-specific thing. Especially with major version updates (such as in this case). If you are curious, you can find discussions between other developers in other issue threads about rationale behind some of the changes. (i.e. the `g_log_set_writer_func()` change)

As far as the chromium issues, afaik no one else can reproduce it (I certainly can't). You can always try making a new user account and then try opening chromium there to see if it is triggered by some of your settings?

> The indicated is to keep Glib 2.72 to fix.

Probably, at least, until the individual issues are resolved upstream either in glib or in the applications using glib (depending on the specific issue) in which case we would either import the patches or wait for a new release.