lucaschessR2 icon indicating copy to clipboard operation
lucaschessR2 copied to clipboard

Play against an engine screen gets frozen on linux

Open Tecvoc opened this issue 2 years ago • 2 comments

I have downloaded the latest version Version R2.09b and then followed this guide to install it on linux.

When i tried playing against the engine after doing python3 LucasR.py it kept getting stuck with the initial message of "Reading the list of engines".

Initially while installing when you try to make the engines executable with sh ./RunEngines it gives warning for two folders not found namely fox and foxcub, they are expected to be Fox and FoxCub, so i changed the names of these in the bin/OS/linux/RunEngines file.

However later when playing against an engine is selected then the screen gets frozen with message of "Reading the list of engines".

I was eventually able to resolve the bug.

This error is happening due to the line 274, in Code/Configuration, as it is
for engine in ("foxcub", "fox", "maia", "irina", "rodentii"):

which i changed as for engine in ("FoxCub", "Fox", "maia", "irina", "rodentii"):

and it started to work.

This naming inconsistency of engines is causing the issue.

Also i think a link can be added in the main readme to the above [guide]((http://lucaschess.blogspot.com/2021/07/linux-tutorial-for-creating-installer.html) which helped me to install it. One part missing in the guide is that _fastercode folder needs to be run too, so that could be added in the guide as well.

Tecvoc avatar Jul 23 '23 08:07 Tecvoc

Thanks. There is one inconsistency that I will try to correct. Folder names should be lowercase, in my working copy they are, I don't know why it hasn't been updated correctly on GitHub.

lukasmonk avatar Jul 24 '23 06:07 lukasmonk

I just had the same issue. However, rather than changing the code, I went to change the "Fox" and "FoxCub" folder names respectively to "fox" and "foxcub" within bin/OS/linux/Engines. Also I had to run the chmod +x command for the Fox and FoxCub binary as they were not executable following "git clone" (while the other engines were already set as executable).

jlrdh avatar Aug 06 '23 17:08 jlrdh