Bug 1268636 - [abrt] pychess: PyChess.py:257:run:EOFError: EOF when reading a line
Summary: [abrt] pychess: PyChess.py:257:run:EOFError: EOF when reading a line
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pychess
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bruno Wolff III
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:ddddc1aa8126b7aabfd40d4c3d0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-04 01:01 UTC by Greg
Modified: 2015-12-02 18:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 15:34:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (679 bytes, text/plain)
2015-10-04 01:01 UTC, Greg
no flags Details
File: environ (2.21 KB, text/plain)
2015-10-04 01:01 UTC, Greg
no flags Details

Description Greg 2015-10-04 01:01:29 UTC
Version-Release number of selected component:
pychess-0.10.1-6.fc21

Additional info:
reporter:       libreport-2.3.0
cmdline:        /usr/bin/python -u /usr/lib/python2.7/site-packages/pychess/Players/PyChess.py
executable:     /usr/lib/python2.7/site-packages/pychess/Players/PyChess.py
kernel:         4.1.7-100.fc21.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
PyChess.py:257:run:EOFError: EOF when reading a line

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/pychess/Players/PyChess.py", line 834, in <module>
    pychess.run()
  File "/usr/lib/python2.7/site-packages/pychess/Players/PyChess.py", line 257, in run
    line = raw_input()
EOFError: EOF when reading a line

Local variables in innermost frame:
newColor: 1
k: 'reuse'
lines: ['analyze']
self: <__main__.PyChessCECP instance at 0x7f40b5d09320>
v: 0
line: 'analyze'
stringPairs: ['draw=1', "myname='PyChess 0.10.1'", "variants='normal,nocastle,fischerandom'", 'san=1', 'usermove=1', 'setboard=1', 'sigterm=1', 'analyze=1', 'colors=1', 'reuse=0']

Potential duplicate: bug 1228117

Comment 1 Greg 2015-10-04 01:01:32 UTC
Created attachment 1079688 [details]
File: backtrace

Comment 2 Greg 2015-10-04 01:01:33 UTC
Created attachment 1079689 [details]
File: environ

Comment 3 Greg 2015-10-04 01:03:18 UTC
Hung when rotting board at start of a new game, after several games played wihout a problem.

Comment 4 Fedora End Of Life 2015-11-04 10:21:17 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 5 Fedora End Of Life 2015-12-02 15:34:42 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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