(*** This bug was imported into bugs.kde.org ***) Package: kbackgammon Version: 2.5.0 (using KDE 3.0.0 ) Severity: crash Installed from: RedHat RPMs Compiler: Not Specified OS: Linux OS/Compiler notes: Red Hat 7.3 When running kbackgammon and playing a game on FIBS the application always crashes in the following situation: 1)I just rolled the dice. 2)No move is possible for me all positions are blocked whether I'm coming off the bar or not. 3)I pick up one of my pieces to move before my opponent rolls the dice (I don't always immediately notice when no move is possible so sometimes I'll pick up a piece by accident) 4)As soon as I let go of the piece by letting go of the left mouse button the application crashes. My opponent wonders if I'm dropping the game (the bug usually happens when I'm losing since it only occurs when all my pieces are blocked). One possible solution would be not to allow a piece to be picked up unless a move is possible though fixing this at the source would certainly be better. -Julian (Submitted via bugs.kde.org)
Please compile with debugging and provide a backtrace. this is very time consuming to reproduce. :)
Subject: Re: crashes when no move is possible and a piece is picked up Hi George, --- George Staikos <staikos@kde.org> wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=47803 > > > > > ------- Additional Comments From staikos@kde.org > 2003-02-13 05:01 ------- > Please compile with debugging and provide a > backtrace. this is very time consuming to > reproduce. :) Would help, but I've stopped playing gammon a while ago. Perhaps someone else using the software can do this: it's not too hard for a regular player to generate the bug, it can happen almost every game. I avoided it by not picking up a piece when no move was legal :-) -Julian __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com
Is this bug still present in a recent version of KDE, such as 3.5.8 or KDE 4.0 RC 2?
Closing due to no response by reporter. Please reopen if this bug can be reproduced in a recent version of KDE, such as 4.0.1 or 3.5.9