I've also experienced this bug as well, but I think I've found a fix.

in /usr/share/doc/crafty there is a shell script, what this script does
is that it copies the opening books to a .crafty folder in your homedir
and gives you environmental variables to put in your .bashrc to point to
that directory.

After that, all you have to do is to reload the desktop manager, by
either logging out or rebooting.

Not only will this work as an easy workaround for the bug, but it also
gives you a personal book file with write permissions, allowing crafty
to go into learning mode.

Don't run that script as sudo btw, since it creates the files with the
privileges of whatever user invokes it. Having files in your homedir
with root as owner won't allow you to write to them, thus disabling
learning mode :)

I also changed the crafty.rc to allow it to use both of my cores :3
(change mt=0 to mt=2 where 2 is the number of cpus/cores)

-- 
Crafty does not use the opening book
https://bugs.launchpad.net/bugs/533756
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to