Bug#1016841: bolt: autopkgtest failure with libglib2.0-0=2.73.3-1: g_log_set_writer_func() called multiple times

[Simon McVittie]

Source: bolt
Version: 0.9.2-1
Severity: important
Tags: upstream
User: debian-ci at lists.debian.org
Usertags: needs-update
Forwarded: https://gitlab.freedesktop.org/bolt/bolt/-/issues/181

With GLib 2.73.3 from experimental, bolt's installed-tests started failing:

> 1..6
> # Start of logging tests
> Bail out! GLib-FATAL-ERROR: g_log_set_writer_func() called multiple times
> 
> (/usr/libexec/installed-tests/bolt/test-logging:2158): GLib-ERROR **: 21:55:26.826: g_log_set_writer_func() called multiple times

Since https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2617,
GLib considers it to be a fatal programming error to call
g_log_set_writer_func() more than once. The justification is
that this sets process-global state, with each call overwriting
the effect of previous calls in older versions of GLib; therefore
g_log_set_writer_func() should only be called once, near the beginning of
main() (or possibly from a wrapper function that is similarly documented
as only valid to call once, near the beginning of main()).

I've suggested a possible solution on the upstream issue
https://gitlab.freedesktop.org/bolt/bolt/-/issues/181.

This will become RC when GLib 2.73.x/2.74.x reaches unstable, which I
suspect will need to happen for GNOME 43.

    smcv