This bug was fixed in the package glib2.0 - 2.68.1-1~ubuntu21.04.1

---------------
glib2.0 (2.68.1-1~ubuntu21.04.1) hirsute; urgency=medium

  * debian/{control,gbp.conf}: Update branch refs for hirsute
  * Backport from Debian to hirsute for SRU (LP: #1928001)

glib2.0 (2.68.1-1) experimental; urgency=medium

  * New upstream stable release
  * d/tests/run-with-locales: Avoid FTBFS with locales-all installed

 -- Iain Lane <iain.l...@canonical.com>  Mon, 10 May 2021 18:14:07 +0100

** Changed in: glib2.0 (Ubuntu Hirsute)
       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/1928001

Title:
  [SRU] New stable release 2.68.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Hirsute:
  Fix Released

Bug description:
  [ Description ]

  Take this new upstream stable release.

  * Fix a crash in `GKeyFile` when parsing a file which contains translations
    using a `GKeyFile` instance which has loaded another file previously (#2361)

  * Pin GIO DLL in memory on Windows (!2016)

  * Bugs fixed:
   - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
   - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
   - !2016 GIO W32: Pin gio DLL
   - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
   - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
   - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
   - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ 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.

  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 GNOME terminal, Files and Epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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

Reply via email to