** Description changed:

- When run GNUbg will crash with the error (on the console):
+ [Preamble]
+ I am one of the primary maintainers of the GNUbg project.
  
-     Attempt to unlock mutex that was not locked
-     Aborted (core dumped)
+ [Impact]
+ When a user starts a new match GNUbg will crash with this error (on the 
console):
+ 
+     Attempt to unlock mutex that was not locked
+     Aborted (core dumped)
  
  This issue is a regression that appeared in Ubuntu 14.10 . It wasn't an
- issue in Ubuntu 14.04.
+ issue in Ubuntu 14.04. This bug should be a high priority for this
+ application because this bug renders the software completely unusable.
  
- To reproduce launch GNUbg and click the "New" icon to start a new match.
- Click "Ok" on the match parameters screen (no need to modify the
- settings). The match should start. You may need to hit Control-R to roll
- to roll the dice (alternatively click the middle of the board on the
- right side). Shortly after doing so the application will close down.
+ [Test Case]
+ To reproduce launch GNUbg and click the "New" icon to start a new match. 
Click "Ok" on the match parameters screen (no need to modify the settings). The 
match should start. You may need to hit Control-R to roll to roll the dice 
(alternatively click the middle of the board on the right side). Shortly after 
doing so the application will close down.
  
- This bug is high priority for this application because it renders the
- software unusable.
+ [Regression Potential]
+ The patch/bug fix attached to this report should be reasonably low risk and 
should not impact other software on the users system. Most regressions that may 
result from any new problems that could be introduced are that the analysis 
output may be slightly different. 
+ 
+ Upstream official software releases (1.03.000 and 1.04.000) have been
+ using the fixes in this patch for a few months without any reported
+ issues and as a result are considered well tested by the upstream
+ maintainers.
+ 
+ [Bug cause]
+ New versions of Glib have extra assertions that may reveal hidden bugs. This 
happened with GNUbg. The problem highlighted issues in how we were using 
mutexes (creations/usage/cleanup). Older versions of Glib didn't have these 
newer assertions so the problem had gone undetected in previous releases. 
+ 
+ [Bug history]
+ The set of changes in this patch were applied to the upstream version of 
GNUbg in July 2014 based upon a bug report of a user that was using a PPA 
version of Glib in Ubuntu 14.04. That bug and further information about the 
nature of this issue can be found here: 
https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1346567
+ 
+ There was a report of this bug shortly after 14.10 was release but for
+ some inexplicable reason it was deleted from launchpad.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnubg 1.02.000-2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 15 17:08:35 2014
  InstallationDate: Installed on 2014-10-24 (22 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
-  LANGUAGE=en_CA:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_CA.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_CA:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnubg
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [Preamble]
- I am one of the primary maintainers of the GNUbg project.
+ I am one of the primary upstream maintainers of the GNUbg project.
  
  [Impact]
  When a user starts a new match GNUbg will crash with this error (on the 
console):
  
      Attempt to unlock mutex that was not locked
      Aborted (core dumped)
  
  This issue is a regression that appeared in Ubuntu 14.10 . It wasn't an
  issue in Ubuntu 14.04. This bug should be a high priority for this
  application because this bug renders the software completely unusable.
  
  [Test Case]
  To reproduce launch GNUbg and click the "New" icon to start a new match. 
Click "Ok" on the match parameters screen (no need to modify the settings). The 
match should start. You may need to hit Control-R to roll to roll the dice 
(alternatively click the middle of the board on the right side). Shortly after 
doing so the application will close down.
  
  [Regression Potential]
- The patch/bug fix attached to this report should be reasonably low risk and 
should not impact other software on the users system. Most regressions that may 
result from any new problems that could be introduced are that the analysis 
output may be slightly different. 
+ The patch/bug fix attached to this report should be reasonably low risk and 
should not impact other software on the users system. Most regressions that may 
result from any new problems that could be introduced are that the analysis 
output may be slightly different.
  
  Upstream official software releases (1.03.000 and 1.04.000) have been
  using the fixes in this patch for a few months without any reported
  issues and as a result are considered well tested by the upstream
  maintainers.
  
  [Bug cause]
- New versions of Glib have extra assertions that may reveal hidden bugs. This 
happened with GNUbg. The problem highlighted issues in how we were using 
mutexes (creations/usage/cleanup). Older versions of Glib didn't have these 
newer assertions so the problem had gone undetected in previous releases. 
+ New versions of Glib have extra assertions that may reveal hidden bugs. This 
happened with GNUbg. The problem highlighted issues in how we were using 
mutexes (creations/usage/cleanup). Older versions of Glib didn't have these 
newer assertions so the problem had gone undetected in previous releases.
  
  [Bug history]
  The set of changes in this patch were applied to the upstream version of 
GNUbg in July 2014 based upon a bug report of a user that was using a PPA 
version of Glib in Ubuntu 14.04. That bug and further information about the 
nature of this issue can be found here: 
https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1346567
  
  There was a report of this bug shortly after 14.10 was release but for
  some inexplicable reason it was deleted from launchpad.
- 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnubg 1.02.000-2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 15 17:08:35 2014
  InstallationDate: Installed on 2014-10-24 (22 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnubg
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393105

Title:
  GNUbg crashes shortly after starting game

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1393105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to