Bug#1065022: libglib2.0-0t64: t64 transition breaks the systems

[Leandro Cunha]

Hi

On Thu, Feb 29, 2024 at 12:51 AM Christoph Anton Mitterer
<calestyo at scientia.org> wrote:
>
> Package: libglib2.0-0t64
> Version: 2.78.4-2
> Severity: critical
> Justification: breaks unrelated software
> X-Debbugs-Cc: debian-devel at lists.debian.org
>
> Hey.
>
>
> CCing d-d since there seems some further deeper problem with the t64
> transition (namely lib files getting lost, when "downgrading" i.e.
> reverting).
>
>
> Earlier tonight I've upgraded this day’s packages which included
> numerous that made the t64 transition (see the attached aptitude log
> for the whole process, first the upgrade, and then "bi-secting" to
> find the culprit).
>
> Immediately afterwards, starting GUI programs from the still running
> desktop environment caused failures like:
> $ evince
>
> (evince:17537): GLib-GIO-CRITICAL **: 04:18:22.610: g_settings_schema_source_lookup: assertion 'source != NULL' failed
>
> (evince:17537): GLib-GIO-CRITICAL **: 04:18:22.610: g_settings_schema_source_lookup: assertion 'source != NULL' failed
>
> (evince:17537): GLib-GIO-ERROR **: 04:18:22.658: No GSettings schemas are installed on the system
> Trace/breakpoint trap
> $ gedit
>
> (gedit:17585): GLib-GIO-ERROR **: 04:18:35.012: No GSettings schemas are installed on the system
> Trace/breakpoint trap
> $
>
> I suspected a reboot might be needed but after that even the display
> manager didn't start anymore.
> I saw errors like:
> Feb 29 02:51:14 heisenberg kernel: traps: at-spi-bus-laun[17935] trap int3 ip:7fdceec49587 sp:7ffd0acdade0 error:0 in libglib-2.0.so.0.7800.4[7fdceec05000+99000]
> Feb 29 02:51:52 heisenberg kernel: traps: at-spi-bus-laun[17941] trap int3 ip:7f52e53ee587 sp:7ffcc69b0fc0 error:0 in libglib-2.0.so.0.7800.4[7f52e53aa000+99000]
>
>
> My first guess was glib, so I downgraded that (everything from the source
> package), but that didn't help.
>
> As you can see from the aptitude log, I then moved on downgrade further
> of the previously upgraded packages, several times I've rebooted in-
> between (e.g. after downgrading things like *pam* and *systemd*).
>
> Along the way I saw the most weirdest effects:
> - logind was apprently in some bogus state, which I think might
>   have been the reason, why X/the display manager remained black/hung for
>   several minutes:
>   Feb 29 03:37:21 heisenberg lightdm[139886]: Failed to get list of logind seats: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
>
> - At some point, when installing packages via aptitude
>   # aptitude
>   <here I started the upgrade or downgrade>
>   Performing actions...
>   <here it hang for several minutes... no real CPU/disk load>
>
>   And it also hung at the end shortly after finishing the
>   upgrade/downgrade.
>
> - When downgrading packages that had a t64 transition, sometimes
>   the lib file was gone.
>   I.e. I removed the *t64 package and re-installed the old one
>   and then the .so file for libapt-pkg6.0 and libpam0g was missing.
>   How can that happen?
>
>
> Eventually I downgraded the gcr/gck stuff, and then it worked again.
>
> From that I went forward and upgrade all the various packages again, to
> see where the problem actuall is.
>
> Turns out, it's probably actually libglib.
>
> When I install the first time libglib2.0-0t64 (and purge libglib2.0-0),
> things start to break apart.
> When I re-install libglib2.0-0t64, things work again (it seems regardless
> of the gcr/gck stuff).
>
>
> Long story short:
> @glib maintainers:
> - there's something wrong with the transition (unless even that need for
>   the re-install is already a sign for some deeper issues)
>
> @d-d:
> - How can it happen that purge *t64 packages and at the same time install
>   the previous package, and then the so file is missing?
>   I mean it's clear that they use the same name, but shouldn't DPKG handle
>   the cleanly?
>
> Thanks,
> Chris
>
> PS: I'll attach the aptitude log only to the bug and not to d-d, in
>     order not to spam so many people with it.
>     It's probably anyway uselesss, but might help to find out why
>     downgrading gck/gcr stuff helped first, without re-installing the
>     glib package.
>
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
> Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libglib2.0-0t64 depends on:
> ii  libc6         2.37-15
> ii  libffi8       3.4.6-1
> ii  libmount1     2.39.3-6
> ii  libpcre2-8-0  10.42-4+b1
> ii  libselinux1   3.5-2
> ii  zlib1g        1:1.3.dfsg-3+b1
>
> Versions of packages libglib2.0-0t64 recommends:
> ii  libglib2.0-data   2.78.4-2
> ii  shared-mime-info  2.4-1
> ii  xdg-user-dirs     0.18-1
>
> Versions of packages libglib2.0-0t64 suggests:
> pn  low-memory-monitor  <none>
>
> -- no debconf information

Jeremy uploaded glib 2.0 to experimental which fixes such problems,
here it broke the entire GNOME interface after installation and
Chromium which is in unstable installs this package causing such
problems. I installed 2.79.3-2 from experimental which apparently
resolved the issues by even having GDM back and all GNOME interface.

-- 
Cheers,
Leandro Cunha