GTK apps crashing with "Attempt to unlock mutex that was not locked"

[onesandzeroes]

Attempting to run some GTK apps (e.g. pyrenamer) on 14.10 results in an immediate crash, with the message "Attempt to unlock mutex that was not locked".

https://bugzilla.gnome.org/show_bug.cgi?id=735428 seems to be the relevant upstream bug, and there is a patch here: https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec

To some extent, this seems to be the result of individual projects using GTK incorrectly, and some fixes have been made to those individual projects.

*However*, I am also seeing this bug occur in a closed source third party application, Stata 13. As Emmanuele Bassi mentions in the Gnome bug thread, there are probably a lot of applications out in the wild affected by the same issue, that in some cases cannot be fixed, so it would be good if a fix could be included in the versions of GTK that Ubuntu ships.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libgtk-3-0 3.12.2-0ubuntu9
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 2 10:05:20 2014
InstallationDate: Installed on 2014-04-24 (160 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to utopic on 2014-10-01 (0 days ago)

[onesandzeroes (marius-mather)]

I have just checked and I am able to run both Stata and PyRenamer successfully by installing the libglib2.0 and libgtk2.0 packages from Trusty. (Apologies if I have reported this against gtk-3.0 if it is actually a v2.0 issue, the research I did suggested it was happening in GTK in general).

[Vlad Orlov (monsta)]

I see GTK+3 in Utopic received the patch, but you need to patch GTK+2 as well:

https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=fbf38d16bcc26630f0f721d266509f5bc292f606

[onesandzeroes (marius-mather)]

Things are now working as expected after the latest batch of updates, OK to close/mark as resolved.