Open GoogleCodeExporter opened 9 years ago
Original comment by gbtami
on 10 Nov 2013 at 11:51
Unfortunately I can't reproduce these.
1. Can you produce the same freeze with other engines?
2. Do you have a log from FICS crashes?
Original comment by gbtami
on 11 Nov 2013 at 10:05
Hi gbtami!
It works on my computer, doesn't work on my laptop. Tried purge and
reinstall via console. Won't do. New install as bad as old one. Any idea?
Cheers Peer
Am 11.11.2013 23:05, schrieb pychess@googlecode.com:
Original comment by p...@vielfarbich.de
on 12 Nov 2013 at 12:24
Hi Peer!
Seems it some kind of threading issue (race condition?). Can you reproduce it
with other installed chess engines, like glaurung, sjeng, crafty, etc.? Can you
attach a .log file from a FICS crash, please too?
Original comment by gbtami
on 12 Nov 2013 at 8:54
Original comment by gbtami
on 19 Nov 2013 at 10:59
Hi gbtami!
No I can't reproduce it with other chess engines like eboard or chess or scid.
It's special.
I have pychess running on two machines, desktop and laptop. The laptop shows
all the crashes as described above, the desktop meanwhile some, too, but not
all.
With the desktop I am able to store games at least, but it freezes too, when I
use Fics and i.e. call for a rematch, or it closes down while opening.
I would love to dsend you a Fics crash report - but where ad how to find?
Cheers Peer
Original comment by p...@vielfarbich.de
on 19 Nov 2013 at 1:36
I deinstalled several times incl.the hidden pychess files - no better. Then I
downgraded to pychess 0.10.1beta1, which is no better for me. At least it
didn't close down during a game on fics the last days.
Original comment by p...@vielfarbich.de
on 19 Nov 2013 at 1:57
eboard and scid are not chess engines (I know nothing about chess), they are
chess client (GUI) programs. Chess engines are console programs which plays
chess in command line or you can install a client (GUI) like
xboard/eboard/scid/pychess to play against them. Can you reproduce the freezes
only with playing against stockfish engine or playing against other engines
too? You can see the list of your installed engines in menu Edit->Engines.
I like to see a .log file regarding a FICS crash too. It's in a hidden folder,
under
your homedirectory, named ".local/share/pychess/"
Original comment by gbtami
on 19 Nov 2013 at 3:23
Hi!
It's the same with all engines. I have GnuChess, Pychess of course, Stockfish
and Sjeng. No difference. The freezing not only happens with FICS, it happens
when offline, too, with actions like Save or Offer Undo i.e.
Here comes the log of the very recent crash - I played one just for you ;-)
I downgraded to 10.1 again, because with the Beta it even get's worse, but same
picture here as there.
For the freezes, it doesn't make a difference, if I play against a computer or
a human.
I ended the game (lost because of same stupid mistakes and because I ran out of
time ;-9)
Tell if you need else.
Thanks!
Peer
Original comment by p...@vielfarbich.de
on 19 Nov 2013 at 9:52
Attachments:
After ending, regularly only force quit will close PyChess.
Original comment by p...@vielfarbich.de
on 19 Nov 2013 at 9:55
The .log created with 0.10.1beta1 doesn't help here, because we fixed several
bugs since. If you can reproduce the crash with 0.12beta4 it's .log may help.
Can you describe a bit more detailed (step by step) how you produce a crash and
what you see exactly?
Anyhow, thx. for helping and for your patience!
Original comment by gbtami
on 20 Nov 2013 at 10:11
Hi gbtami!
First: it's my pleasure. Nice to have people out there who do such nice stuff
;-) So thank you!
I played another game and reproduced one of the typical and regularly crashes,
when trying to save the game after it's finished. But this happens only on my
laptop. The log is attached.
But on both machines no offer undo or offer rematch i.e. working. All except
logging in to FICS or playing a normal game against computer does not work
during a game and after it. It always freezes and I have to force shut or even
restart to bring it back to life.
Maybe apython issue or compiz too? I am no expert and have no clue. Just trying
reinstall won't do anything. Crazy enough: the first version, before I updated
worked fine and since then no way, even if I downgrade.
By the way: I miss something, which I thought is great for training purposes:
the function to undo moves. That allows to try other ways, until the better way
is found. Analizing after a game is lost is great, but for training and
building an inner eye it would be great to have this function back. I read the
post of the father, who said who would not like it for his son, but I would
like it for me ;-)
Cheers Peer
Original comment by p...@vielfarbich.de
on 20 Nov 2013 at 6:08
Attachments:
One more typical crash. Happens not always but frequently.
While opening Pychess, it closes down with a crash report. See attached log.
One more suggestion regarding the design: The white figures in most designs are
greyed out when on black field, because they are just shown with their frame. I
would prefer to see them fully white as opposite to black, because they are
psychologically better seen that way. It's a common problem with chess players
not to see the obvious anyway. Worse if the figures are greyed out ... ;-)
Better would be an ivory background with distinct white and black figures IMO.
Cheers Peer
Original comment by p...@vielfarbich.de
on 20 Nov 2013 at 11:28
Attachments:
Are you sure you are testing 0.12beta4? Your attached .log files seems played
with the old 0.10.1beta. 0.12beta4 logs always start with "PyChess Anderssen
0.12beta4" in first line.
I think I don't understand your "function to undo moves" suggestion. Isn't it
the same as "offer undo"?
There are no frame only figurines in 0.12beta4 themes at all, but I agree we
need some more themes for black and white board fields in the future (ivory,
wood, etc.)
Original comment by gbtami
on 21 Nov 2013 at 11:30
Hi!
Yes I should. I deinstalled the older Pychess version including
.config/pychess, .local/share/pychess and .cache/pychess, downloaded the most
recent .deb (pychess 0.12beta4-1) file from your site, reinstalled Pychess from
the Ubuntu repositories and updated afterwards using the deb.
But as I wrote, i don't understand why even the older version on the
repositories is also not working as it did before.
But I tried now: deinstallation of pychess and the 3 hidden files as mentioned
above and reinstallation just the most recent deb. The appearance is different
now, but still freezing, when I try to save a game. I attached the log, which
clearly indicates it's the pychess 0.12beta4-1.
If I sm the only one to experience this: Is there a way to check the python
part, if there might be a bug?
Regarding undo: before one could simply take one or more moves back to try
other variations to continue the game - try and error for the best solution ;-)
Now the 'Offer Undo' tab is a different approach, as far as I understand,
because I don't want to offer undo, I want to undo my own moves instead. But I
could not try, because it freezes always anyway, if I try to test it.
Cheers Peer
Original comment by p...@vielfarbich.de
on 22 Nov 2013 at 1:32
Attachments:
I played another one against an engine. Attached the log.
Same thing: Saving doesn't work, freezing instead and I have to 'Force Quit'.
Original comment by p...@vielfarbich.de
on 22 Nov 2013 at 2:29
Attachments:
[deleted comment]
[deleted comment]
Could you please supply an exact set of steps on how to reproduce the freeze,
as well as whether it is what we call, "reproduceable", which means that by
following some set of steps, you encounter the problem/freeze every single
time. And don't forget to attach the resulting log file. Thanks for your time.
Here is an example:
What steps will reproduce the problem?
1) Play a standard chess rules game against pychess
2) Go to Game -> Save Game
3) Click "Save" Button
What is the expected output? What do you see instead?
pychess freezes
Does it happen every time?
Yes
Original comment by mattgatto
on 1 Dec 2013 at 1:49
Did the freeze problems start after upgrading to Ubuntu 13.10?
Original comment by mattgatto
on 1 Dec 2013 at 1:53
Hi Mattgatto!
Let me first answer your questions.
The freezes (or crashes have nothing to do with upgrading Ubuntu to 13.10,
because I was using it since I installed Pychess from repositories the first
time.
The version from the Ubuntu repositories is 0.10.1beta. There it was working
like a charme, all functions I tested.
The problems came up when I downloaded the most recent deb, which is PyChess
Anderssen 0.12beta4.
After updating the crashes and freezes happen regularly and constantly, when
doing certain operations.
I run Pychess on a laptop and on a desktop, both under Ubuntu 13.10.
On my desktop it works now all after deleting and reinstalling, but not on my
laptop.
Logging in to Fics and playing online and offline games works on my laptop, too.
Everything else only on my desktop only works on the desktop.
On the laptop it takes a second, when I try to save the game, then the window
turns grey and freezes. It will not respond any further to any command. I have
to force shut Pychess in order to continue or play a new game or even to
restart the computer (sometimes).
On both machines all commands of the 'Actions' or 'Saving' sections result in
an immediate freeze after about two seconds, no matter if I play online or
offline against a human opponent or against an engine.
1) Play a standard or any other game against Pychess or on FICS.
2) Apply on of the 'Action' commands during a game or try to save after a game.
Click one of the buttons like 'offer remis' or 'save under' i.e.
4) Pychesss take about 2-3 seconds, greys out and freezes (no reaction on any
command including 'close').
5) I have then to 'Force shut' Pychess (sometimes even shut down the computer)
in order to be able to restart for a new game. If I don't apply any 'Actions'
or try to 'Save' I can start a new game after finishing one.
6) It happens every time.
You find the logs in #15 and #16 already. #15 shows a game on FICS, #16 shows
an offline game against an engine, both played on my laptop.
Peer
Original comment by p...@vielfarbich.de
on 1 Dec 2013 at 11:29
Hi Peer. So in the example of 'Saving', when _exactly_ does the freeze occur?
Immediately after doing 'Game' -> 'Save' in the pychess window menu? Or after
you click the 'Save' button in the 'Save Game' dialog? Judging from your log
file, it seems like the latter, because it appears to have saved the file
correctly. Is that correct?
Original comment by mattgatto
on 1 Dec 2013 at 7:44
Hi Mattgatto!
It freezes after 'Games' / 'Save Games' or 'Save Games under' It's the only way
I see to save Games.
And it freezes after whatever 'Action' commands I use during a game - may it
be online or offline.
I then have to right click with my mouse on the Pychess desktop symbol and
choose 'force quit' in order to be able to restart Pychess. Trying to close or
anything else in the Pychess window would not be possible any more and won't
show any effect.
Yes it saves a file - I just did a nonsense game against an engine and attach
the file it saved. But I can't open it with Pychess - it freezes when I try as
well and again, I have to 'Force shut' as described above.
Peer
Original comment by p...@vielfarbich.de
on 1 Dec 2013 at 9:30
Attachments:
Try finding 'gamenanny.py' on your system like this:
$ locate gamenanny.py |grep '/usr/lib.*gamenanny.py$'
/usr/lib/python2.7/site-packages/pychess/widgets/gamenanny.py
And apply this patch, (or just comment out the line
'gamewidget.status(message)' as shown below) and see if that fixes it:
diff -r e6484d8894ce lib/pychess/widgets/gamenanny.py
--- a/lib/pychess/widgets/gamenanny.py Thu Nov 28 15:31:05 2013 -0800
+++ b/lib/pychess/widgets/gamenanny.py Sun Dec 01 16:59:13 2013 -0800
@@ -163,7 +163,7 @@
def _set_statusbar (gamewidget, message):
assert type(message) is str or type(message) is unicode
- gamewidget.status(message)
+# gamewidget.status(message)
def game_paused (gamemodel, gmwidg):
s = _("The game is paused")
Original comment by mattgatto
on 2 Dec 2013 at 1:01
Hi mattgatto!
Tried both ways. Gamenanny is located in:
/usr/lib/pymodules/python2.7/pychess/widgets/gamenanny.py
!.) Tried with command 'diff': Command unknown, file not found
2.) Commented out like this:
sudo nano /usr/lib/pymodules/python2.7/pychess/widgets/gamenanny.py
3.) In Nano:
def _set_statusbar (gamewidget, message):
assert type(message) is str or type(message) is unicode
# gamewidget.status(message)
4.) Save with 'Strg O' / Close with 'Strg X'
5.) Played a game against computer
6.) Tried to save the game.
7.) Pychess greys out and freezes
8.) Have to use 'Force shut' to close and start again.
Original comment by p...@vielfarbich.de
on 2 Dec 2013 at 5:09
What about after doing:
$ sudo rm /usr/lib/pymodules/python2.7/pychess/widgets/gamenanny.py[c,o]
Original comment by mattgatto
on 6 Dec 2013 at 11:26
Hi mattgatto,
Thanks for the response, still the same after doing the sudo rm command you
suggested. Pychess freezes, when I try to save a game or do any command of the
'ACTION' section.
The logfile is attached.
P.
Original comment by p...@vielfarbich.de
on 7 Dec 2013 at 9:37
Attachments:
Hi Peer!
Can you try the latest pychess from source, please? Install mercurial from your
Ubuntu repo first (sudo apt-get install mercurial). Then you have to checkout
pychess here http://code.google.com/p/pychess/source/checkout
Then standing in the dir where you downloaded it, start with:
PYTHONPATH=lib/ python pychess
Original comment by gbtami
on 9 Dec 2013 at 12:07
Hi gbtami!
So sorry. I did. Same thing: freeze as described above.
I always play on one and doubleplay and save parallel on another desktop to be
able to analyze games.
Maybe I should reset my whole ubuntu system, as I justed updated from 10.04 to
10.10 ...
Thank you for your support anyhow!
Peer
Original comment by p...@vielfarbich.de
on 9 Dec 2013 at 4:56
Are you sure you run the latest source? You can check it on Help->About dialog
box. You should see Rev. 47e9bb52f643 under the PyChess Anderssen 0.12beta4
text.
Original comment by gbtami
on 9 Dec 2013 at 8:24
Hi!
Yes it says it's Rev. 47e9bb52f643
The Console says upon starting pyches:
peer@peer-Akoya-P7818:~/pychess$ PYTHONPATH=lib/ python pychess
Warning: eco.db not find, run pgn2ecodb.sh
sys:1: Warning: GChildWatchSource: Exit status of a child process was
requested but ECHILD was received by waitpid(). Most likely the process
is ignoring SIGCHLD, or some other thread is invoking waitpid() with a
nonpositive first argument; either behavior can break applications that
use g_child_watch_add()/g_spawn_sync() either directly or indirectly.
Does that give you any clue?
Cheers Peer
Am 09.12.2013 21:24, schrieb pychess@googlecode.com:
Original comment by p...@vielfarbich.de
on 9 Dec 2013 at 9:23
Hi!
Yes it says it's Rev. 47e9bb52f643
The Console says upon starting pyches:
peer@peer-Akoya-P7818:~/pychess$ PYTHONPATH=lib/ python pychess
Warning: eco.db not find, run pgn2ecodb.sh
sys:1: Warning: GChildWatchSource: Exit status of a child process was requested
but ECHILD was received by waitpid(). Most likely the process is ignoring
SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first
argument; either behavior can break applications that use
g_child_watch_add()/g_spawn_sync() either directly or indirectly.
Does that give you any clue?
Cheers Peer
Original comment by p...@vielfarbich.de
on 9 Dec 2013 at 9:23
No, these are warnings only, not related to freeze.
Thx. anyhow!
Original comment by gbtami
on 9 Dec 2013 at 9:53
Make sure you run it with the "./pychess" too or it will run the one installed
on the system:
$ PYTHONPATH=lib/ python ./pychess
Original comment by mattgatto
on 10 Dec 2013 at 2:33
Issue 826 has been merged into this issue.
Original comment by gbtami
on 24 Dec 2013 at 4:02
Regarding the connection to FICS in general: I am using SCID now instead, works
like a charme, no disconnection whatsoever, except if the opponent is cutting
connection, which is considered a forfeit and shows me I am the winner ;-) But
no disconnection, easy continuation with another opponent to choose.
I miss some functions of PYCHESS though and also like the interface and it's
easy-to-use design more than SCID, especially regarding the analysis of a game
and choosing an existing offer for a game and the communication between players
- in SCID it's all console work, which makes it more complicated and slower. On
the other hand SCID is much more sophisticated and has many more functions
(which I don't use, but some professional players might like).
Original comment by p...@vielfarbich.de
on 24 Dec 2013 at 9:29
Finally I was able to reproduce this on 13.10 in Virtualbox. The problem was I
used Xubuntu before. After installing ubuntu-desktop I got the freeze. I tried
ubuntu-gnome-desktop too, and it's ok, no freeze. So the reason is unity global
menu! After some googleing the solution is:
UBUNTU_MENUPROXY= PYTHONPATH=lib python ./pychess
Can you try this, please!
Original comment by gbtami
on 24 Dec 2013 at 11:06
[deleted comment]
Hi gbtami!
Tried. Console says:
/usr/bin/python: can't find '__main__' module in './pychess'
What to do?
Original comment by p...@vielfarbich.de
on 25 Dec 2013 at 12:02
Hi gbtami!
Found the solution myself. Played one game and saved it and used "resign" on
"action" panel - worked all like a charme and no freeze.
The complete way to solution is:
Use the latest and source as follows, cd to the file and start via Console with
the above command afterwards.
Step by step (all commands in the console):
1. sudo apt-get install mercurial
2. Enter your password upon request and let it install. Close console
afterwards.
2. Then open your browser and go to:
3. http://code.google.com/p/pychess/source/checkout
4. Save the directory to a file you prefer.
5. Enter the installed directory via console on your computer. In my case this
is in /home/peer/pychess, so the command is:
cd /home/peer/pychess
6. Start pychess in the console with:
UBUNTU_MENUPROXY= PYTHONPATH=lib python ./pychess
There you are!
Original comment by p...@vielfarbich.de
on 25 Dec 2013 at 12:50
Peer, thx for trying it!
Original comment by gbtami
on 25 Dec 2013 at 1:03
Original comment by mattgatto
on 25 Dec 2013 at 1:39
Hi Mattgatto!
After intense playing I can say it's really nicely working, all commands work.
There are only some few crashes at start up with online chess FICS and
sometimes, when I do chat, it might shut down without warning. But only
sometimes.
I do love Ubuntu, but I don't get, why the testing of major innovations is not
tested before implementing it. It really keeps people away.
There was this long story of new sound architecture, which needed intense
workaround, and the next thing is unity - it is crashing again and again on my
system, not shutting down though, just occcasionally, but creating crash
announcements form the system in a row.
Jobbs understand, that design and functionality comes first - design with
Ubuntu is nice, and function in general as well, but then happen those obvious
blunders, which could have easily avoided by testing a bit in advance. Alas ...
thak you mattgatto and gbtami for your support!!
Original comment by p...@vielfarbich.de
on 29 Dec 2013 at 4:35
Can you produce these remaining few crashes (start up FICS, and doing chat)
using Gnome or Xfce desktops too?
Original comment by gbtami
on 29 Dec 2013 at 4:43
I am using the szandard Ubuntu desktop, that comes shipped with it. So I would
need a Gnome or Xfce for testing first. Do I have to run Virtualbox for it or
is there an easier way to try?
I found a minor issue: when chatting, only part of the conversation is shown in
the dialogue window of the gaming screen. To see all, I have to go to the main
dialogue menu.
Original comment by p...@vielfarbich.de
on 29 Dec 2013 at 6:31
I'm not sure how well this will work for Ubuntu 13.10, but:
http://www.omgubuntu.co.uk/2013/04/gnome-3-8-ppa-for-ubuntu-gnome
Original comment by mattgatto
on 29 Dec 2013 at 8:31
You can install gnome 3 and xfce DE with:
sudo apt-get install ubuntu-gnome-desktop
sudo apt-get install xfce4
On login you can choose wich DE you want to start with.
Original comment by gbtami
on 30 Dec 2013 at 7:08
Hi!
Thanks, I am just doing the install, will test today and let you know right
afterwards, how it works out.
Regarding Ubuntu ... OMG - great ;-)
They would just have to have someone DAU with a MEDION Computer to test and
would know within 2 days, what is working and what is not, and two coders for
max. 5 days - problems solved.
I am rather DAU and it took me just a day to experience the problems, just a
week, to collect parts of the solutions in the net, write them down in a user
friendly and DAU oriented way and publish them for those who experienced those
Ubuntu problems as well - who were quite many - which made me a top spot of
workaround knowledge online ;-) ... as DAU!
Ubuntu could be in a position as Apple by now ... seeing all the major windows
illnesses - NSA not to be the latest, but a major and most serious argument for
even stubborn windows users, to change systems. Alas ...
I heard, they even employ someone for the purpose of testing ...
Original comment by p...@vielfarbich.de
on 30 Dec 2013 at 1:21
It's not free of risk to install Gnome 3.10 in Ubuntu 13.10, there are some
changes needed and there are some bugs, but this is best way - including UNDO,
if problems arise:
http://www.webupd8.org/2013/09/how-to-install-gnome-310-in-ubuntu-1310.html
Original comment by p...@vielfarbich.de
on 30 Dec 2013 at 2:26
This is how to install Gnome 3.10 in Ubuntu 13.10 step by step.
Original comment by p...@vielfarbich.de
on 30 Dec 2013 at 5:05
Attachments:
Original issue reported on code.google.com by
p...@vielfarbich.de
on 10 Nov 2013 at 10:41