gdbusconnection: Explicitly destroy an idle source on cleanup

Bug #2022916 reported by Mike Gabriel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GLib
New
Unknown
glib2.0 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

In Ubuntu Touch we run into regular unit test freezes of lomiri-app-launch (formerly known as ubuntu-app-launch) based on some race time conditions (number of CPUs to build/test on, CPU speed, etc.).

As it turned out, the game changer is a commit in glib2.0 upstream:
https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17

It would be super-cool to see this commit applied on top of glib2.0 in Ubuntu focal and Ubuntu jammy.

Thanks+Greets,
Mike (aka sunweaver @ Debian, working for the UBports core dev team these days)

Revision history for this message
Mike Gabriel (sunweaver) wrote :
tags: added: patch-accepted-upstream
Revision history for this message
Sebastien Bacher (seb128) wrote :

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
status: New → Fix Released
Changed in glib:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.