Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
elementary OS |
New
|
Undecided
|
Unassigned |
Bug Description
In freya, gtk+2.0 is currently on version 2.24.23-0ubuntu1.3, while glib is on 2.42.2-
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:/
[2]: https:/
[3]: https:/