I have moved this to confirmed. I am working on a fix. It appears that there has been a real but hidden bug in our code since 2.32 related to locking/unlocking/freeing mutexes. It appears this bug didn't exist on WIN32 and any platform with glib<2.32. Although it is hidden it could be causing unexpected problems.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346567 Title: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1346567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs