GNOME Bugzilla – Bug 560142
when starting fullscreened, Aisleriot can't leave fullscreen mode
Last modified: 2009-07-13 10:38:04 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-games/+bug/296028 " Steps to reproduce the bug: 1- Start Free-Cell and make it full-screen. 2- Exit the game and re-start. It is still full-screen. 3- Press F11 to exit full-screen. Expected : the app changes to a window Actual Results: the app changes to a window but flicks straight back to full-screen. It is then impossible to exit full-screen or access the menu." This isn't reproducible with mahjongg or blackjack. Thanks you,
Please don't file bugs in the "freecell" component. Moving to the right component, which is aisleriot.
Confirmed with metacity 2.24.0 (compositing not enabled). The sequence of events is this: Press F11 to exit FS mode. Aisleriot does gtk_window_unfullscreen() - window-state-event with changed_mask FULLSCREEN and new_state 0 - window-state-event with changed_mask FULLSCREEN and new_state FULLSCREEN -> this is not an aisleriot bug; someone else is sending the new fullscreen request. This used to work... -> let's try metacity; possibly a dup.
Btw, the difference between fullscreen-unfullscreen and fullscreen-exit-start-unfullscreen in aisleriot is that the window is fullscreened before it's shown (gtk_window_fullscreen) for the first time.
With metacity logging, I see that after unfullscreening the window, metacity tries to re-size it to the screen's size and treats that as fullscreen: GEOMETRY: Move/resize 0x400003 (Treize) to 0,0 1024x768 from 6,36 616x446 GEOMETRY: Constraining 0x400003 (Treize) in move from 6,36 616x446 to 0,0 1024x768 WORKAREA: Window 0x400003 (Treize) xinerama 0 has work area 0,0 1024 x 768 Avertissement du gestionnaire de fenêtres : Treating resize request of legacy application 0x400003 (Treize) as a fullscreen request WINDOW_OPS: Fullscreening 0x400003 (Treize) That points to this being caused by bug #461927.
And the latest patch in bug 461927 does fix this problem. -> Duplicate. *** This bug has been marked as a duplicate of 461927 ***
*** Bug 588429 has been marked as a duplicate of this bug. ***