Activity log for bug #1393105

Date Who What changed Old value New value Message
2014-11-16 00:23:15 Michael Petch bug added bug
2014-11-16 00:33:23 Michael Petch attachment added patch to fix glib bugs https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1393105/+attachment/4261561/+files/gnubg_1.02.000.diff
2014-11-16 01:12:02 Michael Petch description When run GNUbg will crash with the 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. 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. 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) [Preamble] I am one of the primary 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. 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 SourcePackage: gnubg UpgradeStatus: No upgrade log present (probably fresh install)
2014-11-16 01:16:04 Michael Petch description [Preamble] I am one of the primary 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. 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 SourcePackage: gnubg UpgradeStatus: No upgrade log present (probably fresh install) [Preamble] 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. 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 SourcePackage: gnubg UpgradeStatus: No upgrade log present (probably fresh install)
2014-11-16 04:23:37 Ubuntu Foundations Team Bug Bot tags amd64 apport-bug utopic amd64 apport-bug patch utopic
2014-11-16 04:23:47 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors Team
2014-11-16 16:15:54 Michael Petch description [Preamble] 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. 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 SourcePackage: gnubg UpgradeStatus: No upgrade log present (probably fresh install) [Preamble] 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 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. 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 (>= 2.41.2) have extra assertions that may reveal hidden bugs. The Glib changes highlighted problems 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 although the bug is present but may invoke undefined behaviour. [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 . Russ Allbery the Debian maintainer closed that bug off as fixed by landing it in Vivid Vervet (15.04) by releasing version 1.03.001-1 . There was a user 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)
2014-11-16 16:31:54 Adam Conrad nominated for series Ubuntu Utopic
2014-11-16 16:31:54 Adam Conrad bug task added gnubg (Ubuntu Utopic)
2014-11-16 16:31:54 Adam Conrad nominated for series Ubuntu Trusty
2014-11-16 16:31:54 Adam Conrad bug task added gnubg (Ubuntu Trusty)
2014-11-16 16:32:05 Adam Conrad gnubg (Ubuntu): status New Fix Released
2014-11-16 16:43:31 Michael Petch attachment removed patch to fix glib bugs (debdiff) https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1393105/+attachment/4261561/+files/gnubg_1.02.000.diff
2014-11-16 16:48:15 Michael Petch attachment added Patch (debdiff) to resolve this bug https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1393105/+attachment/4261906/+files/gnubg_1.02.000.diff
2014-11-16 22:24:41 Michael Petch attachment removed Patch (debdiff) to resolve this bug https://bugs.launchpad.net/ubuntu/utopic/+source/gnubg/+bug/1393105/+attachment/4261906/+files/gnubg_1.02.000.diff
2014-11-16 22:25:18 Michael Petch attachment added Patch (debdiff) to resolve this bug https://bugs.launchpad.net/ubuntu/utopic/+source/gnubg/+bug/1393105/+attachment/4262106/+files/gnubg_1.02.000.diff
2015-02-11 00:49:17 Brian Murray removed subscriber Ubuntu Sponsors Team
2015-02-11 00:49:20 Brian Murray gnubg (Ubuntu Trusty): status New In Progress
2015-02-11 00:49:23 Brian Murray gnubg (Ubuntu Trusty): assignee Brian Murray (brian-murray)
2015-02-11 00:49:25 Brian Murray gnubg (Ubuntu Trusty): importance Undecided High
2015-02-11 00:49:28 Brian Murray gnubg (Ubuntu Utopic): status New Triaged
2015-02-11 00:49:31 Brian Murray gnubg (Ubuntu Utopic): importance Undecided High
2015-02-11 16:44:52 Chris J Arges gnubg (Ubuntu Trusty): status In Progress Fix Committed
2015-02-11 16:44:55 Chris J Arges bug added subscriber Ubuntu Stable Release Updates Team
2015-02-11 16:44:58 Chris J Arges bug added subscriber SRU Verification
2015-02-11 16:44:59 Chris J Arges tags amd64 apport-bug patch utopic amd64 apport-bug patch utopic verification-needed
2015-02-12 14:01:17 Michael Petch tags amd64 apport-bug patch utopic verification-needed amd64 apport-bug patch utopic verification-failed
2015-02-24 04:00:00 imbezol bug added subscriber imbezol
2015-05-21 01:01:01 Julio Anso bug added subscriber Julio Anso
2015-08-13 03:38:54 Mathew Hodson gnubg (Ubuntu Trusty): status Fix Committed Confirmed
2015-08-13 03:39:47 Mathew Hodson gnubg (Ubuntu Trusty): assignee Brian Murray (brian-murray)
2015-08-13 16:02:20 Brian Murray gnubg (Ubuntu Utopic): status Triaged Won't Fix
2015-10-26 07:20:08 Mathew Hodson gnubg (Ubuntu): importance Undecided High
2015-10-26 07:20:54 Mathew Hodson gnubg (Ubuntu Trusty): status Confirmed Triaged
2015-10-26 15:54:02 Mathew Hodson bug added subscriber Ubuntu Sponsors Team
2015-10-26 15:54:15 Mathew Hodson bug added subscriber Ubuntu Review Team
2015-11-10 15:39:56 Marc Deslauriers removed subscriber Ubuntu Sponsors Team
2016-05-12 13:41:50 Martin Pitt removed subscriber Ubuntu Stable Release Updates Team
2016-05-12 13:41:51 Martin Pitt removed subscriber SRU Verification