← Back to team overview

desktop-packages team mailing list archive

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

 

Thank you for your bug report. The commit message states it's needed for
glib > 2.41 or trusty has glib 2.40, are you sure your issue is the same
one?

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1517983

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

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  In trusty, gtk+2.0 is currently on version 2.24.23-0ubuntu.

  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, 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 fix seems to have landed in upstream[2] and utopic[3], but not in trusty.

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1517983/+subscriptions


References