Since the last update, a solitarire game I play has begun disabling the mouse, leaving me unable to click anywhere in the game's client area. I can still click on the [X] in the title bar in order to kill the game.
When I start gnome-mahjongg, it plays normally, with mouse clicks immediately taking effect. When the game ends, if I start a second game without restarting the app, mouse clicks take effect only after 1/3 or 1/2 second. Click, wait, tile is selected. Click again, wait, a second tile is selected. Wait, tiles are removed.
The alternative sometimes happens instead. I click, the tile is selected, after which the game's client area becomes totally unresponsive to the mouse. Anywhere I click, nothing happens at all. As I mentioned, the system areas still work okay, so I can click [X] to close the game. Then, upon restarting, all works fine again.
SUSPECTED ROOT CAUSE: When playing additional games without restarting the application, something continues to build up -- undo stack? -- until behavior is affected, and eventually game play stops. Restarting the app begins with empty data structures, after which the build-up begins again.
So, this doesn't stop me from playing Mahjongg, but it's incredibly annoying. Anybody else seeing this?
