Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#31783 - [gnome-games] glChess engines don't play
Attached to Project:
Arch Linux
Opened by Robbie Smith (zoqaeski) - Wednesday, 03 October 2012, 09:13 GMT
Last edited by Jan de Groot (JGC) - Friday, 05 October 2012, 12:48 GMT
Opened by Robbie Smith (zoqaeski) - Wednesday, 03 October 2012, 09:13 GMT
Last edited by Jan de Groot (JGC) - Friday, 05 October 2012, 12:48 GMT
|
DetailsDescription:
On my newly-installed Arch system, glChess is not displaying the output of any of the chess engine backends. If I start a game against the computer (regardless of which side I make it), or even try to pit the computer against itself, my cpu usage skyrockets but no moves get made by the computer player, and it acts as though two humans are playing. Furthermore, when the game ends, or I quit the program, the chess engines aren't killed, and they start eating RAM and (eventually) swap space. In typical GNOME (GTK?) fashion, there's no console output when the application is running, so I have no idea what is going on. Additional info: I've got the following chess engines installed: gnuchess 6.0.2-1 fruit 2.1-1 phalanx 22-3 sjeng 11.2-3 (I think this might be better posted as a bug upstream, so I'll do that too, but their bugtracker doesn't seem to be very active.) Steps to reproduce: Start a new game in glChess, setting one or both the players to a computer. Game starts, but no moves are made by the computer player although the CPU usage increases dramatically. Quitting or ending the game doesn't stop engines, which have to be manually killed. |
This task depends upon
Closed by Jan de Groot (JGC)
Friday, 05 October 2012, 12:48 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in gnome-unstable
Friday, 05 October 2012, 12:48 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in gnome-unstable
Screenshot of system usage by the engines after I quit glchess: http://ompldr.org/vZnFnNQ