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 m
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 downgrad
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
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
** 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 notification
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 so
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 ut
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 rend
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 shor
@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 dis
@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 i
@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 Ubu
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 thi
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. A
** 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/13931
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 opi
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.la
** 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 is
** 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 cras
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
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"
** 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.launchp
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
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:
gnub
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 glib<2.32. Although it is hidden it could be
causing unexp
** 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.ne
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
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~
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 t
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 co
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:
Normall
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
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). Ins
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 use
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 subscribe
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 g
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 wh
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 subscrib
*** 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
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
** 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/dp
--
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/ubu
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 pr
43 matches
Mail list logo
