touch-packages team mailing list archive

[Ryan Lortie <desrt@xxxxxxxx>]

The new mutex implementation detects the (error) case when you try to
unlock a mutex that is not locked.

Callers are supposed to acquire the Gtk lock before calling gtk_main()
and I guess gnome-do isn't doing that...

POSIX silently ignores this...

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

Title:
  Do.exe crashed with SIGABRT in __GI_raise()

Status in “glib2.0” package in Ubuntu:
  Invalid
Status in “gnome-do” package in Ubuntu:
  Confirmed

Bug description:
  Do.exe crashed with SIGABRT in __GI_raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-do 0.9-1build1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 18 17:47:01 2014
  ExecutablePath: /usr/lib/gnome-do/Do.exe
  InstallationDate: Installed on 2014-05-16 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterpreterPath: /usr/bin/mono-sgen
  ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
  Signal: 6
  SourcePackage: gnome-do
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
   __GI_abort () at abort.c:89
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? ()
  Title: Do.exe crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions