GNOME Bugzilla – Bug 677017
Display error: after a move erroneously disappear a piece
Last modified: 2013-05-01 21:39:16 UTC
Display error: after the next move "34. Bh6" erroneously disappear the pawn h5. [BlackLevel "hard"] 1. e4 c5 2. c3 Nf6 3. e5 Nd5 4. d4 cxd4 5. Nf3 b6 6. Bc4 Bb7 7. O-O e6 8. Qxd4 Nc6 9. Qe4 Na5 10. Bxd5 Bxd5 11. Qf4 Be7 12. Ng5 O-O 13. h4 d6 14. exd6 Bxd6 15. Qg4 Qc7 16. Nd2 Rae8 17. Nd2e4 Bh2+ 18. Kh1 Be5 19. Ng3 f5 20. Qh5 g6 21. Qd1 Bxg3 22. fxg3 Qxg3 23. Nf3 Bxf3 24. Rxf3 Qxh4+ 25. Rh3 Rd8 26. Qe2 Qe4 27. Be3 Nc4 28. Re1 Rd3 29. Qf2 e5 30. Rh4 Qc6 31. Bg5 f4 32. Rh2 Rf5 33. Qh4 h5 *
Wild guess: You are sure that this is not due to En passant? See http://cs.wikipedia.org/wiki/Bran%C3%AD_mimochodem If it is not, please attach an example game here with the above moves saved in it.
(In reply to comment #1) > Wild guess: You are sure that this is not due to En passant? See > http://cs.wikipedia.org/wiki/Bran%C3%AD_mimochodem > > If it is not, please attach an example game here with the above moves saved in > it. hi André, notice, the move is with Bishop (“34. Bh6”), so it is not “en passant”, and the entire game before the move is in description.
Yeah, but I am reeeeally lazy to play all these steps manually if an attached game could just make me jump to the 34th step and save me 5 minutes. :)
(In reply to comment #3) > Yeah, but I am reeeeally lazy to play all these steps manually if an attached > game could just make me jump to the 34th step and save me 5 minutes. :) André, open editor, then copy and past the moves from description (plus “34. Bh6”) and save as PGN-file. I am not at home and I have not the saved game.
Hey jozef :) Could you maybe provide such a save game nonetheless? Thanks! Anyway, reopening as there is sufficient information now.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in v3.6.0. *** This bug has been marked as a duplicate of bug 683101 ***