Closed GoogleCodeExporter closed 9 years ago
Just want you to know that somehow miraculously, do not know if by new pychess
release in karmic or by python or some other package add/remove, but the main
thing
is that pychess now works fine from release as well as latest svn version.
Starts fine, engine discovery ok, connecting to fics stable. Of course, it still
crashes once and then but now I can help you finding bugs, translating, play
chess. :-)
Really happy here, thanks for PyChess.
Original comment by pe3...@gmail.com
on 15 Oct 2009 at 11:25
This bugs seems to be fixed for me now too under Fedora 11.
Original comment by dean.brettle
on 16 Oct 2009 at 6:45
Is this bug finally fixed now? Can we close the issue? (I have Ubuntu 8.10 and
PyChess runs fine for me!)
-John
Original comment by zollo.j...@gmail.com
on 29 Jan 2010 at 1:00
I think I found out how to reproduce this:
Enable "Assistive Technologies" in the preferences. On my Ubuntu 9.10 Karmic
system it's in System >
Preferences > Assistive Technologies. I've attached a screenshot of the dialog
too.
Original comment by mattgatto
on 13 Feb 2010 at 8:56
Attachments:
Sometimes its locks up in the initial "Discovering Engines" dialog. Sometimes
it doesn't even paint a
window before it locks up (after which it locks up the whole GNOME session. And
sometimes I get as far
as clicking the "Start Game" button in the main window before it locks up.
Original comment by mattgatto
on 13 Feb 2010 at 8:59
Issue 556 has been merged into this issue.
Original comment by gbtami
on 28 Apr 2010 at 1:51
I had PyChess running great, but after enabling "Assistive Technologies" it
locks up on starting new games. It seams to be the same problem as Matt's.
Probably though, that should be put in another bug, as there is no "Dumping
core".
Issue 556 also seams different from this. It seams more like a drawing issue.
Original comment by lobais
on 24 Jun 2010 at 12:48
Original comment by gbtami
on 21 Mar 2013 at 8:11
Issue 660 has been merged into this issue.
Original comment by gbtami
on 21 Apr 2013 at 7:19
I guess this issue was an aggregation of different problems for different
people. But the hang hasn't been reproduceable for me for awhile now, and the
workaround for it described in comment 54, disabling Assistive Technologies,
wouldn't work anyway anymore, because there is no more assistive technologies
preferences, AFAIK.
Original comment by mattgatto
on 2 Aug 2013 at 4:22
Original issue reported on code.google.com by
regns...@gmail.com
on 4 Aug 2008 at 11:11