gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnubg (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Gnubg crashes after starting.
It didn't use to crash. But it starting crashing after a recent update of Ubuntu (within the second week of July).
The Ubuntu version, as well as one built from the GNU project's sources crash in the same way.
In the terminal there is printed:
Attempt to unlock mutex that was not locked
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnubg 1.02.000-2
ProcVersionSign
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jul 21 14:25:16 2014
InstallationDate: Installed on 2012-09-02 (687 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120902)
SourcePackage: gnubg
UpgradeStatus: Upgraded to trusty on 2014-05-09 (73 days ago)
Changed in gnubg (Ubuntu): | |
assignee: | nobody → Michael Petch (mpetch) |
status: | Incomplete → Confirmed |
Changed in gnubg (Ubuntu): | |
assignee: | Michael Petch (mpetch) → nobody |
status: | Fix Committed → Confirmed |
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 <email address hidden> . 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