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 698677 - File -> "New" causes main window of GIMP to disappear in fullscreen mode
File -> "New" causes main window of GIMP to disappear in fullscreen mode
Status: RESOLVED DUPLICATE of bug 698641
Product: mutter
Classification: Core
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-04-23 16:17 UTC by Bastian Ilsø
Modified: 2013-04-23 18:45 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screencast: Main window dissapearing in fullscreen. (452.00 KB, application/x-compressed-tar)
2013-04-23 16:17 UTC, Bastian Ilsø 		Details

Description Bastian Ilsø 2013-04-23 16:17:44 UTC 
Created attachment 242260 [details]
Screencast: Main window dissapearing in fullscreen.

I usually work in GIMP with GNOME 3.6 - I recently upgraded to GNOME 3.8 and now the fullscreen window disappear whenever GIMP opens another window. For example when pressing Ctrl+N to create a new image. Or when pulling a Dock out of its position and make it float. It is very confusing behavior in general and prevents me from putting a dock I by accident made floating back into its position in the main window.

Reproduction steps:
-> Open Gimp -> Windows -> Single-Window mode
-> Press F11 to go fullscreen
-> Go to File -> New.

The main window should now disappear.
Comment 1 Michael Natterer 2013-04-23 18:41:54 UTC 
My first guess would be to report this against GNOME. After all, GNOME
has changed, not GIMP. Reassigning.
Comment 2 Florian Müllner 2013-04-23 18:45:03 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 698641 ***