Hey Mike. While I understand that the issue is annoying there is always
risk in doing change to a library of the base system as libglib and
difficult to verify that there are not side effect of any of the
software using it. If there is no real user visible impact the benefit
is probably not worth the risk and effort for Ubuntu. Perhaps you could
set up a ppa or local env for your CI including the fix instead?
I'm closing the bug since the issue is fixed in the current version, it
doesn't prevent us to target older series if we decide to go the SRU way
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => Low
** Changed in: glib2.0 (Ubuntu)
Status: New => Fix Released
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2925
https://gitlab.gnome.org/GNOME/glib/-/issues/2925
** Also affects: glib via
https://gitlab.gnome.org/GNOME/glib/-/issues/2925
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2022916
Title:
gdbusconnection: Explicitly destroy an idle source on cleanup
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2022916/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
