This bug was fixed in the package glib2.0 - 2.72.4-0ubuntu1
---------------
glib2.0 (2.72.4-0ubuntu1) jammy; urgency=medium
* New upstream release (LP: #1980408)
* Update testfilemonitor-Skip-if-we-are-avoiding-flaky-tests.patch
for new testfilemonitor test.
-- Jeremy Bicha <jbi...@ubuntu.com> Wed, 12 Oct 2022 14:59:04 -0400
** Changed in: glib2.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1980408
Title:
Update glib to 2.72.4
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Jammy:
Fix Released
Bug description:
Impact
------
There is a new bugfix release in the stable 2.72 series
https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.4/NEWS
Test Case 1
-----------
glib has an extensive test suite.
Failing tests will fail the build.
This update will also trigger a lot of autopkgtests.
Ensure that there aren't autopgktest regressions triggered by this
update and that the builds complete successfully
Test Case 2
-----------
Pretty much all parts of GNOME use GLib, so test anything in the desktop that
you can. If you reboot the machine and can get to the desktop, that's already
tested GLib extensively. But also run applications like the terminal, the file
browser and epiphany-browser
What Could Go Wrong
-------------------
This update contains fixes in multiple places so multiple apps could be
affected. The consequences of a broken GLib can range from some functions
returning bad results sometimes, which have minimal runtime implications, up to
the system simply crashing all the time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
