Your message dated Sun, 03 Mar 2024 01:49:32 +0000 with message-id <e1rgayq-006c2d...@fasolo.debian.org> and subject line Bug#1065022: fixed in glib2.0 2.79.3-3 has caused the Debian Bug report #1065022, regarding libglib2.0-0t64: transition from libglib2.0-0 breaks GSettings, GIO modules to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libglib2.0-0t64 Version: 2.78.4-2 Severity: critical Justification: breaks unrelated software X-Debbugs-Cc: debian-de...@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
--- End Message ---
--- Begin Message ---Source: glib2.0 Source-Version: 2.79.3-3 Done: Simon McVittie <s...@debian.org> We believe that the bug you reported is fixed in the latest version of glib2.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie <s...@debian.org> (supplier of updated glib2.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 02 Mar 2024 23:07:12 +0000 Source: glib2.0 Architecture: source Version: 2.79.3-3 Distribution: experimental Urgency: medium Maintainer: Debian GNOME Maintainers <pkg-gnome-maintain...@lists.alioth.debian.org> Changed-By: Simon McVittie <s...@debian.org> Closes: 1065022 Changes: glib2.0 (2.79.3-3) experimental; urgency=medium . * Merge pending packaging from unstable - Mention #1065280 in 2.79.3-1 changelog entry * d/libglib2.0-0t64.preinst: Remove libglib2.0-0 postrm to avoid file loss during the time64 transition (Closes: #1065022) * d/tests/manual/1065022.sh: Add a manual reproducer for #1065022 * d/libglib2.0-0t64.postrm: Only clean up giomodule.cache during purge. This matches the behaviour that we have had for gschemas.compiled since 2012, with similar reasoning: if we remove this file during remove, then during upgrades there is a window between old-postrm and new-postinst during which giomodule.cache is missing. * d/libglib2.0-0t64.postrm: Avoid recurrence of #1065022 in the future. If at some point in the future we have another transition as extensive as time64, then libglib2.0-0t64 could conceivably be replaced by some other package, for example libglib2.0-0xyz. If that happens, we need to avoid deletion of gschemas.compiled and giomodule.cache, otherwise we will have another bug similar to #1065022. * d/tests/1065022-futureproofing: Add a test for recurrence of #1065022. This test-case depends on several implementation details which might cause it to regress for reasons that are not genuinely release-critical, so it is marked as flaky. Checksums-Sha1: 17f2acfcde8a3543c35ce6d15016c4e1b6736189 4507 glib2.0_2.79.3-3.dsc ba077097f00cad603e8f9f4c3ab0d39b600b83ba 129052 glib2.0_2.79.3-3.debian.tar.xz 32de4fbbc445d4b0edfbe069de227b9e2c2017cb 7593 glib2.0_2.79.3-3_source.buildinfo Checksums-Sha256: f19a118c5808231a5c36a8bdea82a99f52db9b49bcec124c1d4bc98519ca9faa 4507 glib2.0_2.79.3-3.dsc be37dffdd661326eeeb53d9011b818303138ab373b826d341a7a40ce29c67e37 129052 glib2.0_2.79.3-3.debian.tar.xz 77a63d939b56b831ebb07393766fef755d636bb7f5998c193e958283cd41cb87 7593 glib2.0_2.79.3-3_source.buildinfo Files: 1b160670305eeed23cde7a7634e9402b 4507 libs optional glib2.0_2.79.3-3.dsc b468bde94524600e7a07e1222ead8242 129052 libs optional glib2.0_2.79.3-3.debian.tar.xz d7437f59ef2643765e3360526ed676bd 7593 libs optional glib2.0_2.79.3-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmXj00kACgkQ4FrhR4+B TE9wQA/+IBqjGj8cr2sBzO64aNAm3n3oHxqYZPVw/IVjhqpTexx3TrOdaVcIncN4 Wge8v26cLj+ouh2Jf1nF6OJIAKM8RehuKRNt0tc8n1hrc29wnH9HGvfSL2+URrCP 6oC5rjjRQXMFGCRjcaCJFgkjRrn7EM49d2Tb72wx6MJcuJ38igCicC5H75n7jvT5 G86HzP6y9eKhkVQbvAruT6iHnHnXCibujHuk6HAWZnt9TUm909ke4Zy9nH4MNOEQ 8lS6CYfV776vBhbhyXfR0K6REHwdx7WWkQFdzAm/O+g8tPJq5Xfa0Exf2WlH2cd6 1Dl/UxBlB1Xr3bOH7ULxd7lREpZ90YCVu1saEyf2z3FpTGjZQJSI+x5LaxxKMT+m +RAINntq4JSWMSozioNLk+nL+ZsfI/JkZRfvC0ec2mPWnZ9v8YHYPQT1xOgzAIbx Sqo1yoQAPwwUEr/6HAq9bSBwVMnVsmsj/fMKs1CBsSd+M6ZwIAHTh32ijSxTR1LF aPr4LGFgoIxDfHtOyPOznQ2F6a9IwfsXNCAOTSiaMniT3uzuc0sopflYSHQpfR94 cbbEuj5+bpsAGk5fw8CU6IEO/5USKISMcQwa0WOJE+gcmC+6qDgmbCnv2Yxan0KC UOOrap4EoYiWeAWZLS54DmPtA7sb/iQCGkUHFXNjo/De9q2FcvY= =jpJH -----END PGP SIGNATURE-----
pgp1JaPsuohXB.pgp
Description: PGP signature
--- End Message ---
