touch-packages team mailing list archive

[onesandzeroes <1376530@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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)

** Affects: gtk+3.0 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1376530

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

Status in “gtk+3.0” package in Ubuntu:
  New

Bug description:
  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)

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