Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet

[Claus Strasburger]

In freya, gtk+2.0 is currently on version 2.24.23-0ubuntu1.3, while glib is on 2.42.2-0ubuntu1~14.04~ricotz0 (from http://ppa.launchpad.net/elementary-os/os-patches/ubuntu/).

Sadly, there is a feature change in glib>2.40, which together with gtk in version 2.24.23 leads to the mentioned error message "Attempt to unlock mutex that was not locked" on many gtk2 apps.

The commit specified here[1] fixes a bug where using libgtk+2.0 in an unidiomatic manner leads to a SIGABRT when starting the app.
I know that unidiomatic behaviour is not supported per-se, but there are a whole bunch of "legacy" apps that are hard to update. Examples include IntelliJ IDEA, OpenXenManager, pidgin, and numerous others.

Is there a chance of getting libgtk+2 updated to a version that in includes [1], or getting that commit backported to trusty?
The gtk fix seems to have landed in debian jessie[2] and ubuntu utopic[3], but not in trusty or freya.

So either libglib should not be on 2.40, or libgtk should get an update. Is that possible?

Thanks,
Claus Strasburger

[1]: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=fbf38d16bcc26630f0f721d266509f5bc292f606
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758619
[3]: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1376530