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 614664 - A completed puzzle not marked done due to puzzle ambiguity
A completed puzzle not marked done due to puzzle ambiguity
Status: RESOLVED DUPLICATE of bug 608907
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
2.28.x
Other opensolaris
: Normal enhancement
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-02 14:22 UTC by Þór S.
Modified: 2010-04-11 20:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
A screenshot of the game. The tracker tepicts the ambiguous numbers. (108.33 KB, image/png)
2010-04-02 14:22 UTC, Þór S. 		Details

Description Þór S. 2010-04-02 14:22:22 UTC 
Created attachment 157754 [details]
A screenshot of the game. The tracker tepicts the ambiguous numbers.

I got the following puzzle solution:

179-542-683
352-698-147
648-137-529
-
785-413-296
436-529-871
291-876-354
-
513-984-762
864-721-935
927-365-418

The squares that were empty when the ambiguity came up were:

... ... ...
... .xx ...
... ... ...

... ... ...
... x.x ...
... xx. ...

... xx. ...
... xx. ...
... ... ...

Of course, if the player manages to full all squares and resolve an ambiguity, the games should be considered solved, even if the numerical order is not the same as in the generated puzzle.
Comment 1 Þór S. 2010-04-05 02:40:03 UTC 
An additional error is that in easy mode, it says I took 44 seconds to finish when really I took 9 minutes....
Comment 2 Jim Ross 2010-04-11 05:53:32 UTC 
Þór, there is a patch that fixes the problems you encountered with not winning a game after ambiguities.  Please see Bug 608907 for a description of that problem.

Also, that 44 second problem has been fixed.  See Bug 562782 that one.

Patches have been committed to the repository for both of these issues, so they should be fixed with the next release.
Comment 3 Thomas Andersen 2010-04-11 20:19:25 UTC 
Since this is already fixed in 608907 I'm marking it as a duplicate of that bug.

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