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 770099 - Pause and Resume GUI problem
Pause and Resume GUI problem
Status: RESOLVED DUPLICATE of bug 766118
Product: gnome-sudoku
Classification: Applications
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-sudoku-maint
gnome-sudoku-maint
Depends on:
Blocks:
 
 
Reported: 2016-08-18 16:29 UTC by Sajjad Heydari
Modified: 2016-08-19 16:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sajjad Heydari 2016-08-18 16:29:10 UTC 
When clicking Pause and Resume, the screen stays the same unless somehow it is refreshed. (EX: clicking on another window)

If I click on Pause, the board is still visible unless I click on another window (and if I click on one tile, only that till is grayed out).

When clicking on Resume, the board is still grayed out, unless I click on the board (or another window).

More info:

Version: 3.20.4
Gnome 3 ArchLinux
gnome-shell version: 3.20.3-1
Comment 1 André Klapper 2016-08-18 16:42:18 UTC 
Which behavior is unexpected, and what is the expected behavior instead?
Comment 2 Sajjad Heydari 2016-08-18 16:44:43 UTC 
I expect the pause button to grey out the board (which it doesn't unless I click on another window, or click on each tile individually)

and I expect the resume button to clear the board (which it doesn't unless I click on the board or on another window)
Comment 3 Michael Catanzaro 2016-08-19 16:03:07 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution.
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

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