Howdy, I'm one of the upstream maintainers and it appears someone else reported a similar problem with a recent update. I installed Ubuntu 14.04 from scratch and installed the product and it ran okay.
With that being said a clean environment may be hiding the problem. I'd like you to attach a copy of your gnubgautorc file to this bug or email a copy directly to mpe...@gnubg.org . This file is found in in your user directory in a folder called .gnubg . So that would be the file: ~/.gnubg/gnubgautorc (Tilde is your home directory) After sending me a copy of the file please do the following. Close all copies of GNUbg. Go to your home directory and rename the .gnubg directory to .gnubgold (rename it do not delete it). Run GNU Backgammon again. It should detect that the ~/.gnubg directory doesn't exist and rebuild a new one with default settings. I am curious if this bug still exists if you do this? Since I can't reproduce this, one theory is that it is a specific setting from an older version of GNUbg is causing the problem. Resetting to defaults will tell me if that is the case. Sending your existing gnubgautorc file allows me to test with the exact settings being used. Thanks -- 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
