Unsubscribing ubuntu-sponsors as there is no actionable item.
Once an updated debdiff is posted, please subscribe ubuntu-sponsors
again. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393105
** Changed in: gnubg (Ubuntu)
Importance: Undecided => High
** Changed in: gnubg (Ubuntu Trusty)
Status: Confirmed => Triaged
--
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:
** Changed in: gnubg (Ubuntu Utopic)
Status: Triaged => Won't Fix
--
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 notificatio
** Changed in: gnubg (Ubuntu Trusty)
Status: Fix Committed => Confirmed
** Changed in: gnubg (Ubuntu Trusty)
Assignee: Brian Murray (brian-murray) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I experience the bug on Elementary OS Freya. How can I fix this?
--
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
** 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
Once it builds in trusty-proposed the plan is to copy the package 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/1393105
Title:
GNUbg crashes shortly after starting game
To manag
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
Was Utopic going to be fixed as well?
Thanks
--
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:
htt
Hello Michael, or anyone else affected,
Accepted gnubg into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/gnubg/1.02.000-2ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
I've uploaded this to the Trusty queue for review by the SRU team.
** Changed in: gnubg (Ubuntu Trusty)
Status: New => In Progress
** Changed in: gnubg (Ubuntu Trusty)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: gnubg (Ubuntu Trusty)
Importance: Undecided
** 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
Given the following facts:
1) The package is at the same version in both trusty and utopic
2) The bug can only be reproduced on utopic, but obviously exists in both
I propose the following unorthodox SRU procedure:
1) The SRU is uploaded to trusty-proposed, so it builds with trusty level deps
2)
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
Based on the description, looks like this should be SRUed to both trusty
and utopic, despite utopic being the only one with a glib that exposes
the bug.
** Also affects: gnubg (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: gnubg (Ubuntu Trusty)
Importance: Undecid
Based on the description, looks like this should be SRUed to both trusty
and utopic, despite utopic being the only one with a glibc that exposes
the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** 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
The attachment "patch to fix glib bugs" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and
** 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
24 matches
Mail list logo