Bug 62108 - KBackgammon doesn't handle the doubling cube well
Summary: KBackgammon doesn't handle the doubling cube well
Alias: None
Product: kbackgammon
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: Alexander Smirnov
Depends on:
Reported: 2003-08-04 13:58 UTC by Daniel Schepler
Modified: 2018-09-02 22:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Schepler 2003-08-04 13:58:04 UTC
Version:            (using KDE KDE 3.1.3)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc version 3.3.1 20030728 (Debian prerelease) 
OS:          Linux

(This is forwarded from Debian bug #202362.)

When playing kbackgammon, I configured it to use the GNU Backgammon
engine, as the others appeared to not work (although this could have
been an issue on my side.)

When playing the game, if you double, the engine may decide to redouble.
In this situation, you can accept or decline; if you accept, the game
invites you to roll the dice. When you click on the icon to roll the
dice, or issue the "roll" command, the game claims that you have already

The full game log (minus commands, unfortunately) is:

Starting a new game.
gnubg rolls 5, lamble rolls 3.
gnubg rolls 5 and 3.
Please roll or double
lamble doubles.
gnubg accepts and immediately redoubles to 4.
Please wait for lamble to consider the cube before moving.
lamble accepts the cube at 4.
Please roll
You already did roll the dice.
You already did roll the dice.

Attempting to move worked, but the game got itself into a very peculiar
state, claiming (amongst other things) that gnubg had rolled a double 0
(an impossible roll).

Playing a game through without doubling works without a hitch.
Comment 1 FiNeX 2009-08-26 14:43:06 UTC
Changed the default assignee.
Comment 2 Andrew Crouthamel 2018-09-02 22:49:43 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug.