Bug 711620 - [abrt] pychess-0.10-1.fc14: lmove.py:349:parseSAN:ParsingError: ('exf3', u'no Pawn is able to move to f3', '2r1r1k1/1b1nbpp1/pq2pn1p/1p6/3NpP1B/6P1/PPP1N1BP/R1QR2K1 b - - 0 18')
Summary: [abrt] pychess-0.10-1.fc14: lmove.py:349:parseSAN:ParsingError: ('exf3', u'no...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pychess
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bruno Wolff III
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0d579c66
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 23:10 UTC by Héctor Vucetich
Modified: 2012-08-16 12:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 12:43:41 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (1.18 KB, text/plain)
2011-06-07 23:10 UTC, Héctor Vucetich
no flags Details

Description Héctor Vucetich 2011-06-07 23:10:56 UTC
abrt version: 1.1.18
architecture: i686
cmdline: /usr/bin/python -u /usr/lib/python2.7/site-packages/pychess/Players/PyChess.py
component: pychess
executable: /usr/lib/python2.7/site-packages/pychess/Players/PyChess.py
kernel: 2.6.35.13-91.fc14.i686.PAE
package: pychess-0.10-1.fc14
reason: lmove.py:349:parseSAN:ParsingError: ('exf3', u'no Pawn is able to move to f3', '2r1r1k1/1b1nbpp1/pq2pn1p/1p6/3NpP1B/6P1/PPP1N1BP/R1QR2K1 b - - 0 18')
release: Fedora release 14 (Laughlin)
time: 1307485943
uid: 500

backtrace
-----
lmove.py:349:parseSAN:ParsingError: ('exf3', u'no Pawn is able to move to f3', '2r1r1k1/1b1nbpp1/pq2pn1p/1p6/3NpP1B/6P1/PPP1N1BP/R1QR2K1 b - - 0 18')

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/pychess/Players/PyChess.py", line 832, in <module>
    pychess.run()
  File "/usr/lib/python2.7/site-packages/pychess/Players/PyChess.py", line 267, in run
    move = parseAny (self.board, lines[1])
  File "/usr/lib/python2.7/site-packages/pychess/Utils/lutils/lmove.py", line 51, in parseAny
    return parseSAN (board, algnot)
  File "/usr/lib/python2.7/site-packages/pychess/Utils/lutils/lmove.py", line 349, in parseSAN
    raise ParsingError, (san, errstring, board.asFen())
ParsingError: ('exf3', u'no Pawn is able to move to f3', '2r1r1k1/1b1nbpp1/pq2pn1p/1p6/3NpP1B/6P1/PPP1N1BP/R1QR2K1 b - - 0 18')

Local variables in innermost frame:
notat: ''
c: '3'
san: 'exf3'
genAllMoves: <function genAllMoves at 0xa30c02c>
frank: None
move: 3494
tcord: 21
flag: 3
board: Black - -
. . r . r . k . 
. b . n b p p . 
p q . . p n . p 
. p . . . . . . 
. . . N p P . B 
. . . . . . P . 
P P P . N . B P 
R . Q R . . K . 

errstring: u'no Pawn is able to move to f3'
ffile: 4
piece: 1

How to reproduce
-----
1. Play several games against PyChess
2. Replay with rematch button
3. Suddenly Phychess crashes

Comment 1 Héctor Vucetich 2011-06-07 23:10:59 UTC
Created attachment 503587 [details]
File: backtrace

Comment 2 Jeremiah Haremza 2011-06-28 17:29:15 UTC
Package: pychess-0.10-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.happened while playing chess
2.
3.

Comment 3 Fedora Admin XMLRPC Client 2011-07-12 19:42:03 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Bruno Wolff III 2011-09-03 18:39:19 UTC
I have a new test update with a number of post 0.10 upstream fixes. Please try it out and let me know if it fixes this issue and/or causes other issues. Thanks.
https://admin.fedoraproject.org/updates/pychess-0.10.rev2004-1.fc14?_csrf_token=0458b62279c19fbd2e7bd1d82762e6eff5891188

Comment 5 Fedora End Of Life 2012-08-16 12:43:47 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.