Re: [Bug 1680223] [NEW] Crash when exporting to html
I could do one this weekend. On 2017-04-05 20:31, Russ Allbery wrote: > Philippe Michel <1680...@bugs.launchpad.net> writes: > >> It was reported upstream as >> https://savannah.gnu.org/bugs/index.php?50617 and should be fixed there >> with the last revision of render.c. > > Is there a plan to make a new upstream release? I always prefer to > incorporate an upstream release rather than trying to cherry-pick specific > patches. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680223 Title: Crash when exporting to html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1680223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376154] Re: data grid not displaying resultset is blank
I originally did testing with Ubuntu 14.04 and this wasn't an issue as the version of Glib in Ubunty 14.04 predated the change that created this situation. Your output shows that you are using the latest official Ubuntu 14.04 mysql-workbench. This has me curious if somehow your version of Glib has been upgraded through a non-official source? Could you provide me the output from this command: dpkg-query -l libglib2.0-0 | grep glib -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376154 Title: data grid not displaying resultset is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376154] Re: data grid not displaying resultset is blank
Yep that is exactly what is going on 2.42.2-0ubuntu1~14.04~ricotz0 is a much newer version of Glib that causes this problem with mysql-workbench (the problem was introduced as of 2.42). You are going to need to acquire a newer version of mysql-workbench to get around the problem or somehow downgrade Glib. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376154 Title: data grid not displaying resultset is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376154] Re: data grid not displaying resultset is blank
Peter and Angus you will need to open a new bug and tag it as regression-update. Brian Murray said this in his last post In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression- update so we can easily find any regressions. With that being said have you confirmed the latest mysql-workbench is installed? What does the output from this command (open a terminal window) say: dpkg-query -l mysql-workbench-data mysql-workbench | grep mysql -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376154 Title: data grid not displaying resultset is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393105] Re: GNUbg crashes shortly after starting game
** Tags removed: verification-needed ** Tags added: verification-failed -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
As an addendum, it manifests itself differently in Trusty. The application is usable, although it could in theory be unstable with multiple threads under the right conditions. It doesn't crash outright. In Utopic the problem is fatal as it will crash right as you start playing which in effect renders the product unusable on that platform. -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
I originally identified the problem in Utopic, so I would hope it would be fixed there too. AT least that was my wish. -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
If I manually apply the patch to the original source and do a build it works. I noticed when I did the Ubuntu build from source that the patch didn't seem to get properly applied and the code it built was essentially the unmodified code (not patched). The only thing I see wrong was the patch had some fuzz in one of the hunks. Not sure if that is related to the issue or not. If I get a chance tomorrow I'll regenerate a new patch. -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
I spent some time today playing with 1.02.000-2ubuntu1 AMD64 playing against the computer and doing rollouts and analysis. The latter two are processor and thread intensive. I didn't observe any problems that would be related to this fix. I happened to copy the gnubg and gnubg-data files to my utopic system. When I ran it and started a new match it crashed and I saw this: GNU Backgammon 1.02.000 Feb 11 2015 Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 by Gary Wong. Copyright (C) 2013 by Gary Wong and the AUTHORS; for details type `show version'. This program comes with ABSOLUTELY NO WARRANTY; for details type `show warranty'. This is free software, and you are welcome to redistribute it under certain conditions; type `show copying' for details. (No game) set gui showids on (No game) save settings (No game) new match Attempt to unlock mutex that was not locked Aborted (core dumped) The date is clearly correct (Feb 11 2015) but it failed. I then downloaded the source tar ball, the debian.tar.xz and the dsc file. I then built the packaged from source with: dpkg-source -x gnubg_1.02.000-2ubuntu1.dsc and then dpkg-buildpackage -rfakeroot -b Running this release failed as well. I'm going to have to revisit the patch and see if something was missed (in the patch) or if there is some other environment related problem (library change/update etc). At the time (a few months ago) it did work as expected and I had thoroughly tested it. -- 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
[Bug 1376154] Re: data grid not displaying resultset is blank
@Nuno . At a command line what does this command output:
dpkg-query -W -f='${Package} ${Version}\n' 'mysql-workbench*'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376154
Title:
data grid not displaying resultset is blank
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376154] Re: data grid not displaying resultset is blank
@Nuno, the binaries are already made. They are available in the utopic- proposed repository. Utopic-proposed is were the code goes to be tested before it is added to the official Utopic release repository. To learn how to enable the -proposed repository using the GUI or the CLI you can use these instructions: https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376154 Title: data grid not displaying resultset is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155571] Re: Workbench not showing tables or query results in raring
@Andrei: This bug was never associated with Utopic however a new bug was created here: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154 The bug also has a patch and a version released to utopic-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155571 Title: Workbench not showing tables or query results in raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1155571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376154] Re: data grid not displaying resultset is blank
Version 6.1.7+dfsg-1ubuntu1on Utopic works for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376154 Title: data grid not displaying resultset is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393105] Re: GNUbg crashes shortly after starting game
** Description changed: [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. + 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 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 (= 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 + 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 report of this bug shortly after 14.10 was release but for - some inexplicable reason it was deleted from launchpad. + 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) -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
Updated patch (debdiff) to resolve this bug. Updated changelog entry. Original patch didn't include a bug fix to a global variable (shared among threads) that was being optimized away leading to instabilities in the software. ** Patch removed: patch to fix glib bugs (debdiff) https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1393105/+attachment/4261561/+files/gnubg_1.02.000.diff ** Patch added: Patch (debdiff) to resolve this bug https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1393105/+attachment/4261906/+files/gnubg_1.02.000.diff -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
Yes Adam, I concur that this issue is on both Trusty and Utopic thanks for amending the bug. I happened to update my original post earlier while you were commenting and suggested that on other versions with older Glib the issue is present but still invoking undefined behavior. So Trusty in my opinion is potentially unstable albeit with no known crash. This issue with the mutexes hasn't existed for the entire lifetime of our project. This issue was introduced in May 2013 in preparation for our official v1.00.000 release. In particular this set of changes: http://cvs.savannah.gnu.org/viewvc/gnubg/multithread.c?root=gnubgr1=1.74r2=1.75sortby=date The change was to accommodate some structural changes and avoid deprecated functionality in Glib = 2.32.0. Unfortunately this issue slipped through the cracks. As a result, any official Ubuntu releases that used a version of GNUbg 1.0 will not experience this problem (Which is any Ubuntu release before Trusty). That leaves only the GNUbg releases used in Trusty and Utopic as candidates for this change. I don't have commit privileges so need sponsorship on this bug. My understanding of the process is a bit lacking so you will have to bear with me. -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
** Patch 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 ** Patch 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 -- 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
[Bug 1376154] Re: data grid not displaying resultset is blank
This bug manifests itself in a number of different ways. All seem to be related to no data being populated in what should be the ListModel panes. Another way to observe this issue is to run mysql-workbench and open the sakila_full model. Once open double click on one of the tables in the diagram. At the bottom in the middle is a pane that should have a column tab. Click on that tab and should see that it is blank. Normally that pane would have a list of all the fields and their attributes and allow you to add/modify/delete any of the columns. This bug is a regression caused by changes in GLIB = 2.42.2. It is rather severe in that it affects many aspects of the workbench from querying databases to editing the EER disagrams. This bug has been identified previously in Debian here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763356 The issue is a glib regression with glib = 2.42.0 . Oracle provided a patch (referenced in this bug report) here: http://bugs.mysql.com/file.php?id=21874bug_id=74147 The upstream bug associated with that patch can be found here: http://bugs.mysql.com/bug.php?id=74147 This bug has been fixed in Vivd Vervet (15.04) as can be found here: https://launchpad.net/ubuntu/+source/mysql-workbench/6.2.3+dfsg-6 I am attaching a debdiff patch that seems to work well to resolve this issue on Ubuntu Utopic Unicorn (14.10) and is the same patch (libglib2.42.patch) applied to mysql-workbench (6.2.3+dfsg-6) in Vivid Vervet (15.04) ** Patch added: Patch (debdiff) to resolve this bug https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+attachment/4262145/+files/mysql-workbench_6.1.7%2Bdfsg-1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376154 Title: data grid not displaying resultset is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1376154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393105] [NEW] GNUbg crashes shortly after starting game
Public bug reported: 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) ** Affects: gnubg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
I am the primary upstream maintainer for GNUbg. Attached is a patch to fix this bug. This patch is a small subset of the changes that went into GNUbg 1.03.000. to deal with this bug and two other fatal problems These changes were related to issues with improper mutex creation/usage/cleanup as well as a couple instability fixes and were brought about because of changes in newer versions of glib. These fixes are also available if one were to upgrade Ubuntu to use GNUbg 1.03.000 or 1.04.000. ** Patch added: patch to fix glib bugs https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1393105/+attachment/4261561/+files/gnubg_1.02.000.diff -- 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
[Bug 1393105] Re: GNUbg crashes shortly after starting game
** 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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
** Changed in: gnubg (Ubuntu) Status: Fix Committed = Confirmed ** Changed in: gnubg (Ubuntu) Assignee: Michael Petch (mpetch) = (unassigned) -- 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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
If Debian/Ubuntu update to 1.03.000 (or higher) this bug should be fixed ** Changed in: gnubg (Ubuntu) Status: Confirmed = Fix Committed -- 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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
Last night I committed a change to CVS that should resolve this problem. If you could test this latest change out I'd appreciate it. -- 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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
Thanks for the files and trying out that test. That rules it out being 3D related and something bad in gnubgautorc that migrated from an old version. When specifically does it crash? At startup? or do you get the board displayed and are able to play and then it crashes later on? One thing I can think of trying is running gnubg with the -q option: gnubg -q You mentioned you have built from sources. I don't know your tech knowledge but I am wondering if you know or have tried building a debug version (with CFLAGS=-g option) and run gnubg with gdb. A backtrace from GNUbg when it crashes might tell us something. -- 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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
Thanks for the backtraces. It became clear when I observed the output that you were using glib from a PPA that was an unofficial repository. Upon looking at your attached dependency list I believe the reason this crashes on your system and not a stock 14.04 is related to this: libglib2.0-0 2.41.2~git20140714.79e63d4e-0ubuntu1~14.04~ricotz0 [origin: LP-PPA-ricotz-testing] libglib2.0-data 2.41.2~git20140714.79e63d4e-0ubuntu1~14.04~ricotz0 [origin: LP-PPA-ricotz-testing] You seem to be using Rico Tzschichholz gnome-testing which can make a system unstable. In particular I have identified the glib entries above since I believe they are the heart of the problem. It appears that there is likely a bug being detected in GNUbg because of new checks that were added to recent versions of glib. This is most likely a GNUbg bug, I would have to investigate further when I get a chance to try the new glib out on a system. I believe the recent changes to GLib that likely influence this bug is this set of patches (see the part about detecting some mutex bugs): https://bugzilla.gnome.org/show_bug.cgi?id=731986 I believe if you were to downgrade glib back to the official Ubuntu version that GNUbg would run albeit it with a bug that is likely going unnoticed. If you could verify that the official glib works then we have an explanation as to why your system is being affected and not others. ** Bug watch added: GNOME Bug Tracker #731986 https://bugzilla.gnome.org/show_bug.cgi?id=731986 -- 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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
If you have an opportunity there are some things you might want to try with the new glib. I don't see an obvious bug in the code besides the possibility of an optimization being done because a memory location is volatile but isn't marked as such. The first thing to try is building from source and doing so without optimizations CFLAGS=-O0 . Does the problem exist? I'd then like to know the output with it configured with CFLAGS=-DDEBUG_MULTITHREADED . This will display additional text to the console that might help me out. Although you have marked the bug as invalid, I have an interest in these last couple tests so I can check our code. It is possible in the future that Ubuntu will use a newer glib and we'll be revisiting this issue again. That is of course if there isn't a bug on the glib side. -- 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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
** Changed in: gnubg (Ubuntu) Assignee: (unassigned) = Michael Petch (mpetch) ** Changed in: gnubg (Ubuntu) Status: Incomplete = Confirmed -- 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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
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 glib2.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
[Bug 1346567] Re: gnubg crashes soon after starting. Attempt to unlock mutex that was not locked
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
[Bug 932455] Re: GNUBG (backgammon) - Desktop stops responding to mouse clicks
Hi VF, The reason building from source doesn't fix this issue (at present) is because the issue is in Debian Ubuntu systems only, and the workaround is a Debian Ubuntu specific fix. First of all, I'm going to recommend downloading an installing the version you couldn't find (0.90+20120127-3). Installing these packages should create the necessary gnubg.desktop file so that when launched from a gnome3/unity menu it should work properly. You must download gnubg and gnubg-data from these locations: http://launchpadlibrarian.net/103709007/gnubg_0.90%2B20120127-3_amd64.deb http://launchpadlibrarian.net/103697408/gnubg-data_0.90%2B20120127-3_all.deb After downloading you can install them from the command line using: sudo dpkg -i gnubg-data_0.90+20120127-3_all.deb gnubg_0.90+20120127-3_amd64.deb Once these are installed you should be able to launch GNUBG through the GUI using the menus/icons, and there should now be a /usr/share/applications/gnubg.desktop that contains Exec=env LIBOVERLAY_SCROLLBAR=0 gnubg -w . If you are rolling your own build from source you must alter how you launch GNUBG. For example if you rolled your own build from source, you could launch from the source directory using: LIBOVERLAY_SCROLLBAR=0 ./gnubg or if you installed GNUBG from source (and did a 'make install' to the default /usr/local) directory you can launch GNUBG like this: LIBOVERLAY_SCROLLBAR=0 /usr/local/bin/gnubg Let me know how you make out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932455 Title: GNUBG (backgammon) - Desktop stops responding to mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/932455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932455] Re: GNUBG (backgammon) - Desktop stops responding to mouse clicks
If you are using a 32bit system then you'll want to install: http://launchpadlibrarian.net/103697407/gnubg_0.90%2B20120127-3_i386.deb instead of the amd64 version I posted before. The gnubg-data files are the same for both 32/64bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932455 Title: GNUBG (backgammon) - Desktop stops responding to mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/932455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932455] Re: GNUBG (backgammon) - Desktop stops responding to mouse clicks
I have committed a change to the latest GNUBG source code. The change will appear in future source code snapshots after July 1st, 2012 . It is available as of this message in CVS. For those building GNUBG from source, and wish to have GNUBG run properly on Ubuntu you must do the following: Normally you run ./autogen.sh, followed by ./configure, followed by make, and possibly sudo make install . For those familiar with this process, you must alter your configure command slightly to include code to work around this bug and force overlay scrollbars off. the configure process should be amended to be something like: ./configure CFLAGS=-DNO_OVERLAYSCROLLBARS With this change, you should be able to run GNUBG without setting any environment variables ahead of time. The downside is that GNUBG will always run with standard scrollbars (not overlayed ones). This fix is temporary until a proper solution can be put in place (And there is a solution). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932455 Title: GNUBG (backgammon) - Desktop stops responding to mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/932455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002063] Re: gnubg freezes desktop after analysing match
Using a stock 12.04 AMD64 debian system I installed gnubg_0.9 +20120127-3 . Without the modification to the gnubg.desktop file it fails as you describe. If I use a version with LIBOVERLAY_SCROLLBAR=0 it functions properly. This could be an environmental issue of some sort. First off where is the gnubg.desktop file you are modifying? Is it the one in your user directory or one in /usr/share/applications ? When it runs (or you think it runs) with LIBOVERLAY_SCROLLBAR=0 how do the scrollbars appear? Do they appear as standard scroll bars or do they pop out at the edge as you pass over them? I'm asking this question since how they will appear tells me whether LIBOVERLAY_SCROLLBAR=0 was actually working. What desktop environment do you use? Gnome3? Unity? KDE? etc? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002063 Title: gnubg freezes desktop after analysing match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1002063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002063] Re: gnubg freezes desktop after analysing match
Can you do me a favor. Can you remove your GNUBG program from Unity launcher (on the left hand side of the screen) and then find GNUBG again in unity's search and then drag it back onto the launcher. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002063 Title: gnubg freezes desktop after analysing match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1002063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002063] Re: gnubg freezes desktop after analysing match
I should point out that based on the screenshot, overlay scrollbars are still turned on, which means that GNUBG is not being launched with them off. This was why I have requested the procedure above. If that still doesn't work there is the possibility that there is a gnubg.desktop file in your user folder under ~/.local/share/applications . Anything in there will override what is in /usr/share/applications from what I remember. If there is a file there for GNUBG, remove it or make sure that it is a copy of the one in /usr/share/applications. On my system here under 12.04 w/unity it does work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002063 Title: gnubg freezes desktop after analysing match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1002063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002063] Re: gnubg freezes desktop after analysing match
Can you verify that the gnubg.desktop doesn't resolve it. I have 12.04 installed here, the issue is present by default, however when I modify /usr/share/applications/gnubg.desktop it does work. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002063 Title: gnubg freezes desktop after analysing match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1002063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002063] Re: gnubg freezes desktop after analysing match
On a technical note regarding this bug: I have a long term solution for this bug that I will commit to CVS, but it can't be made mainstream until one high priority bug is resolved in the fix itself. GNUBG still uses a deprecated GTKList object, and I have found the scrollbar issues are resolved when we stop using the deprecated GTKList and replace it with GTKTreeView . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002063 Title: gnubg freezes desktop after analysing match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/1002063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 938800] Re: gnubg crashes when analysing matches
*** This bug is a duplicate of bug 932455 *** https://bugs.launchpad.net/bugs/932455 ** This bug has been marked a duplicate of bug 932455 GNUBG (backgammon) - Desktop stops responding to mouse clicks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/938800 Title: gnubg crashes when analysing matches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/938800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932455] Re: GNUBG (backgammon) - Desktop stops responding to mouse clicks
After spending an evening in the debugger I accidentally stumbled upon a temporary solution to get GNUBG functional under Ubuntu 11.10 . The issue involves a feature of Ubuntu's desktop that I despise - those overlay scrollbars (scrollbars that popout past the edge of a window to save real estate inside a widget). For some reason the overlay scrollbars under Ubuntu 11.10 do not work with GNUBG for some *yet* unknown reason. If you want to turn overlay scrollbars off for just GNUBG so that launching from the menu works then do this from a command terminal: sudo nano /usr/share/applications/gnubg.desktop Modify the line that starts with Exec= and replace it with this new one: Exec=env LIBOVERLAY_SCROLLBAR=0 gnubg -w This should allow GNUBG tro run properly, and you will notice it will use standard scrollbars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932455 Title: GNUBG (backgammon) - Desktop stops responding to mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/932455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932455] [NEW] GNUBG (backgammon) - Desktop stops responding to mouse clicks
Public bug reported: Description:Ubuntu 11.10 Release:11.10 Installed: 0.90+20091206-4.1 Candidate: 0.90+20091206-4.1 Version table: *** 0.90+20091206-4.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages 100 /var/lib/dpkg/status This problem also exists on 64bit Ubuntu. This problem doesn't exist on Ubuntu 11.04. If you build from the latest GNUBG source (CVS) the bug still exists. This bug is not found in the product when built/installed on Debian Wheezy or current Sid environments. The bug is high priority since it renders the product and your desktop unusable until the program is killed. To produce the problem start a new match against the computer via File menu/New.../Click GNU Backgammon vs Human/Click OK. Make a few moves against the computer. On the right hand side in the move list under the gnubg column click one of the moves the computer made. At this point the analysis pane will appear below the move list and the mouse fails to respond to mouse clicks on the desktop rendering Ubuntu useless. Killing the application manually does work. Although the mouse doesn't work as expected the keyboard still functions, both on the desktop and in GNUBG. This bug has been reported by a number of users and more info can be found here: http://savannah.gnu.org/bugs/?34864 http://lists.gnu.org/archive/html/bug-gnubg/2012-02/msg6.html ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-center 5.0.3.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Wed Jan 4 18:19:59 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnubg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932455 Title: GNUBG (backgammon) - Desktop stops responding to mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/932455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932455] Re: GNUBG (backgammon) - Desktop stops responding to mouse clicks
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932455 Title: GNUBG (backgammon) - Desktop stops responding to mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/932455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932455] Re: GNUBG (backgammon) - Desktop stops responding to mouse clicks
** Description changed: Description: Ubuntu 11.10 Release: 11.10 - Installed: 0.90+20091206-4.1 - Candidate: 0.90+20091206-4.1 - Version table: - *** 0.90+20091206-4.1 0 - 500 http://ca.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages - 100 /var/lib/dpkg/status + Installed: 0.90+20091206-4.1 + Candidate: 0.90+20091206-4.1 + Version table: + *** 0.90+20091206-4.1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages + 100 /var/lib/dpkg/status This problem also exists on 64bit Ubuntu. This problem doesn't exist on Ubuntu 11.04. If you build from the latest GNUBG source (CVS) the bug still exists. This bug is not found in the product when built/installed on Debian Wheezy or current Sid environments. + + The bug doesn't seem to be related to the X-Server. If I run GNUBG + remotely from Ubuntu onto another Xwindow system via SSH, I get similar + behavior. In this case only GNUBG stops responding to the mouse clicks. The bug is high priority since it renders the product and your desktop unusable until the program is killed. To produce the problem start a new match against the computer via File menu/New.../Click GNU Backgammon vs Human/Click OK. Make a few moves against the computer. On the right hand side in the move list under the gnubg column click one of the moves the computer made. At this point the analysis pane will appear below the move list and the mouse fails to respond to mouse clicks on the desktop rendering Ubuntu useless. Killing the application manually does work. Although the mouse doesn't work as expected the keyboard still functions, both on the desktop and in GNUBG. This bug has been reported by a number of users and more info can be found here: http://savannah.gnu.org/bugs/?34864 http://lists.gnu.org/archive/html/bug-gnubg/2012-02/msg6.html + ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-center 5.0.3.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Wed Jan 4 18:19:59 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) PackageArchitecture: all ProcEnviron: - LANGUAGE=en_CA:en - PATH=(custom, no user) - LANG=en_CA.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_CA:en + PATH=(custom, no user) + LANG=en_CA.UTF-8 + SHELL=/bin/bash SourcePackage: software-center 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/932455 Title: GNUBG (backgammon) - Desktop stops responding to mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnubg/+bug/932455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
