debcrafters-packages team mailing list archive

[Ubuntu SRU Bot <2097496@xxxxxxxxxxxxxxxxxx>]

All autopkgtests for the newly accepted glib2.0 (2.72.4-0ubuntu2.6) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

afterstep/unknown (ppc64el)
almanah/unknown (ppc64el)
apport/2.20.11-0ubuntu82.8 (amd64, i386)
asterisk/unknown (amd64)
automake-1.16/1:1.16.5-1.3 (amd64)
budgie-extras/unknown (amd64, ppc64el)
castle-game-engine/unknown (ppc64el)
cbatticon/unknown (ppc64el)
cluster-glue/1.0.12-20ubuntu3 (arm64, s390x)
cluster-glue/unknown (amd64, i386, ppc64el)
cmake-extras/unknown (ppc64el)
cockpit/unknown (ppc64el)
connman-gtk/unknown (ppc64el)
cudf/unknown (ppc64el)
cups/unknown (ppc64el)
dbus/unknown (i386, ppc64el)
dbus-test-runner/16.10.0~bzr100+repack1-4.1 (s390x)
ddnet/unknown (ppc64el)
feedreader/unknown (ppc64el)
ffmpeg/unknown (ppc64el)
flatpak/unknown (ppc64el)
fluidsynth/unknown (ppc64el)
gcab/unknown (ppc64el)
gconf/unknown (ppc64el)
gdm3/unknown (ppc64el)
geocode-glib/unknown (ppc64el)
gexiv2/unknown (ppc64el)
gfsecret/unknown (ppc64el)
gimp-plugin-registry/9.20200927build1 (ppc64el)
gip/unknown (ppc64el)
gjs/unknown (ppc64el)
goobox/unknown (ppc64el)
gphotofs/0.5-6 (ppc64el)
graphene/1.10.8-1 (ppc64el)
gsequencer/unknown (ppc64el)
gspell/unknown (amd64)
gtherm/unknown (ppc64el)
gtk+3.0/3.24.33-1ubuntu2.2 (s390x)
gtk+3.0/unknown (ppc64el)
gtk4/4.6.9+ds-0ubuntu0.22.04.2 (amd64, ppc64el)
imagemagick/unknown (amd64)
indicator-session/unknown (amd64)
lebiniou/unknown (ppc64el)
libadwaita-1/unknown (ppc64el)
libappimage/unknown (amd64, ppc64el)
libcairo-gobject-perl/unknown (ppc64el)
libgdata/unknown (ppc64el)
libglib-object-introspection-perl/unknown (ppc64el)
libhandy/unknown (ppc64el)
libhandy-1/unknown (ppc64el)
libinsane/unknown (ppc64el)
libnotify/unknown (i386)
libosinfo/unknown (amd64)
libpango-perl/unknown (amd64)
libproxy/unknown (amd64, ppc64el)
libreoffice/1:7.3.7-0ubuntu0.22.04.10 (ppc64el)
libreoffice/unknown (amd64, arm64)
librsvg/unknown (amd64, ppc64el)
libsoup2.4/unknown (amd64, ppc64el)
libtickit/unknown (amd64)
libvirt/unknown (ppc64el)
lua-lgi/unknown (amd64, ppc64el)
mandos/unknown (amd64, ppc64el)
modemmanager-qt/unknown (amd64)
mpsolve/unknown (amd64)
nemo/unknown (amd64)
netatalk/unknown (amd64)
network-manager/unknown (amd64)
ngraph-gtk/unknown (ppc64el)
notify-osd/0.9.35+20.04.20191129-0ubuntu2 (amd64)
notify-osd/unknown (ppc64el)
opencv/unknown (ppc64el)
openjdk-21/unknown (amd64)
openjdk-8/unknown (amd64)
openmsx-catapult/unknown (amd64)
openscad/unknown (ppc64el)
openssh/unknown (amd64)
oss4/unknown (amd64)
ostree/unknown (amd64, ppc64el)
ots/unknown (amd64)
pacemaker/unknown (amd64)
pango1.0/unknown (amd64)
parlatype/unknown (amd64)
pinentry/unknown (amd64)
pipewire/unknown (amd64, ppc64el)
pkg-config/unknown (amd64)
playerctl/unknown (amd64)
plplot/unknown (amd64)
pocketsphinx/unknown (ppc64el)
polkit-qt-1/unknown (amd64)
poppler/unknown (amd64)
praat/unknown (ppc64el)
pulseaudio/unknown (ppc64el)
r-cran-rsvg/unknown (ppc64el)
rifiuti2/unknown (ppc64el)
sbd/unknown (ppc64el)
sigma-align/unknown (ppc64el)
slurm-wlm/unknown (ppc64el)
surf/unknown (ppc64el)
swtpm/0.6.3-0ubuntu3.3 (s390x)
tpm2-abrmd/unknown (ppc64el)
ubiquity/unknown (ppc64el)
udisks2/unknown (ppc64el)
uget/unknown (ppc64el)
uim/unknown (ppc64el)
umockdev/unknown (ppc64el)
upower/unknown (ppc64el)
vim/unknown (ppc64el)
vlc/unknown (ppc64el)
webcamoid/unknown (ppc64el)
winff/unknown (ppc64el)
wireshark/unknown (ppc64el)
wise/unknown (ppc64el)
xdemorse/unknown (ppc64el)
xdg-dbus-proxy/unknown (i386, ppc64el)
xpra/unknown (ppc64el)
xsnow/unknown (ppc64el)
zbar/unknown (ppc64el)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2097496

Title:
  libglib: Crash due to infinite recursion in MIME subclassing

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  Fix Committed
Status in glib2.0 source package in Noble:
  Fix Released
Status in glib2.0 source package in Oracular:
  Fix Released
Status in glib2.0 source package in Plucky:
  Fix Released

Bug description:
  [ Impact ]

  There's an infinite recursion in MIME resolution bug which affects
  processes using gio to resolve certain MIME types.  In my case,
  tracker-miner-fs-3 has been crashing in a loop for weeks due to this
  issue.

  This affects any program that attempts to resolve a "recursive" MIME
  type using glib.

  I reported the issue to the GLib maintainers here:
  https://gitlab.gnome.org/GNOME/glib/-/issues/3601

  The fix is given here: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3714
  The backport to 2.78 is here: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3718

  [ Test Plan ]

  1. Install the mime file from the attachment with:
     $ mkdir -p ~/.local/share/mime/packages
     $ wget https://launchpadlibrarian.net/790257958/js-test.xml -O ~/.local/share/mime/packages/js-test.xml
     $ update-mime-database ~/.local/share/mime
  2. Create a javascript file:
     $ echo "{}" > ~/foo.js
  3. Try to open the file:
     $ xdg-open ~/foo.js
  4. Verify that the file was opened in your default text editor for JavaScript
  5. Verify that the program did not crash

  6. Open the "Files" app
  7. Navigate to the Home directory
  8. Right-click "foo.js"
  9. Verify that Nautilus did not crash
  10. Click "Open With Other Application"
  11. Verify that the dialog says "Opening JavaScript program" files

  To cleanup the created files, you may run these commands:
     $ rm ~/.local/share/mime/packages/js-test.xml
     $ update-mime-database ~/.local/share/mime
     $ rm ~/foo.js

  [ Where problems could occur ]

  The patch will not affect the behaviour of the MIME type resolver except detecting and avoiding infinite subclassing for buggy recursive types.
  The same patch is in place in all newer Ubuntu versions without known side-effects.
  Problems could manifest with file-associations not being honoured in case the MIME type resolver is broken (which is verified in the test plan), or with crashes similar to the ones here reported in the patch is inconclusive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2097496/+subscriptions