Bug 597009
Summary: | [abrt] crash in pychess-0.10-0.4.20100504hg.fc13: engineNest.py:403:getEngineN:IndexError: list index out of range | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Webb <dijit> | ||||
Component: | pychess | Assignee: | Thomas Spura <tomspur> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 13 | CC: | dijit, michel, tomspur | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:8d5a6658 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-05-28 13:21:01 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
David Webb
2010-05-27 22:33:38 UTC
Created attachment 417410 [details]
File: backtrace
Odd, the exact steps on a fresh installation of pychess works just fine. Could you try this? $ mv ~/.config/pychess{,.backup} $ pychess and attempt to reproduce? you can do "rm -r ~/.config/pychess && mv ~/.config/pychess{.backup,}" to get your old configuration back. Also, what are the list of opponents available to pick from? (In reply to comment #2) > Odd, the exact steps on a fresh installation of pychess works just fine. Could > you try this? > > $ mv ~/.config/pychess{,.backup} > $ pychess > > and attempt to reproduce? you can do "rm -r ~/.config/pychess && mv > ~/.config/pychess{.backup,}" to get your old configuration back. > > Also, what are the list of opponents available to pick from? ok, I've since played chess fine... must have been a temp but because I didn't reboot or anything before trying to play after install but each opponent appeared twice on the list... now it's fine again. I don't know whether this is a temp bug, but it certainly doesn't hinder me anymore, so I'm not fussed. Could not reproduce. Probably something that happens only the first time you upgrade, then. The pychess homepage does mention that they recently moved the config file to ~/.config/pychess -- perhaps there's a problem the first time that happens. |