Comment 8 for bug 1393105

Yes Adam, I concur that this issue is on both Trusty and Utopic thanks for amending the bug. I happened to update my original post earlier while you were commenting and suggested that on other versions with older Glib the issue is present but still invoking undefined behavior. So Trusty in my opinion is potentially unstable albeit with no known crash.

This issue with the mutexes hasn't existed for the entire lifetime of our project. This issue was introduced in May 2013 in preparation for our official v1.00.000 release. In particular this set of changes:

http://cvs.savannah.gnu.org/viewvc/gnubg/multithread.c?root=gnubg&r1=1.74&r2=1.75&sortby=date

The change was to accommodate some structural changes and avoid deprecated functionality in Glib >= 2.32.0. Unfortunately this issue slipped through the cracks. As a result, any official Ubuntu releases that used a version of GNUbg < 1.0 will not experience this problem (Which is any Ubuntu release before Trusty). That leaves only the GNUbg releases used in Trusty and Utopic as candidates for this change.

I don't have commit privileges so need sponsorship on this bug. My understanding of the process is a bit lacking so you will have to bear with me.