After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674978 - Iagno: computer moves take too much time
Iagno: computer moves take too much time
Status: RESOLVED DUPLICATE of bug 668553
Product: iagno
Classification: Applications
Component: general
git master
Other Linux
: High critical
: ---
Assigned To: iagno-maint
iagno-maint
: 702815 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-04-27 16:23 UTC by Dmitrij D. Czarkoff
Modified: 2013-08-17 16:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dmitrij D. Czarkoff 2012-04-27 16:23:22 UTC 
Compared to previous versions iagno became much slower on compuer moves. Furthermore, while calculating next move it significantly slows down the graphics.
Comment 1 Kunshan Wang 2012-05-03 00:12:14 UTC 
I have seen this problem, too. I just switched from Fedora 16 to Fedora 17 beta.
The current version is gnome-games-3.4.1-2.fc17

It is fine at start, but in the middle of a game the AI will spend several minutes just to make one move. During the time the AI is thinking, the window (the MainLoop?) hangs up and the tool-bar stopped responding and the window is not re-rendered when moved out of the screen and moved back.

This happens even when the AI level is set to 1.

And the AI seems much easier than in the past. Even level 3 is easy to beat. Suspect this is connected with the slowing problem.
Comment 2 Michael Catanzaro 2013-08-17 16:20:02 UTC 
*** Bug 702815 has been marked as a duplicate of this bug. ***
Comment 3 Michael Catanzaro 2013-08-17 16:21:07 UTC 
Confirming
Comment 4 Michael Catanzaro 2013-08-17 16:23:30 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 668553 ***