Bug 690657

Summary:	Gnome displays an empty screen when only one app is running and is being minimized
Product:	[Fedora] Fedora	Reporter:	George Iosif <giosif>
Component:	gnome-shell	Assignee:	Owen Taylor <otaylor>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	19	CC:	gecko-bugs-nobody, giosif, maxamillion, mcepl, mclasen, otaylor, rstrode, samkraju, stransky, walters
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-08 14:56:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description George Iosif 2011-03-24 23:44:15 UTC

Description of problem:
The new Gnome 3.0 environment is meant not to expose the minimize/maximize/restore buttons any more.
While this works for most applications, Firefox included (when run in normal mode), when Firefox is switched to full-screen mode (by pressing F11), the minimize and restore buttons are displayed.
The minimize button is functional as the browser window will minimize when clicked, but then the result will be an empty desktop, with nothing displayed on it (not even the upper panel).
The only way to revert from this situation is to hit ALT+TAB to restore the Firefox browser window and then switch back to normal mode.

Version-Release number of selected component (if applicable):
firefox-4.0-2.fc15.x86_64
gnome-session-2.91.92-1.fc15.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start Firefox and enable full-screen by pressing F11.
2. Notice the minimize and restore buttons (the close button can be considered to be expected).
3. Click the minimize button.
  
Actual results:
The minimize and restore buttons are shown.
If the minimize button is pressed, the empty desktop is shown, with no intuitive way of getting out.

Expected results:
No minimize and restore buttons should be shown.

Additional info:
I believe the issue here is that those minimize, restore and close buttons that are displayed in Firefox when in full-screen mode are presented by the browser application itself, rather than the window manager.

Comment 1 Matěj Cepl 2011-03-25 10:33:51 UTC

Firefox in the minimized state here behaves the same as any other application (press Alt+F9 with any other Gnome app).

So, the only problem is that there is a minimize button in the full-screen mode. Yeah, there is.

Comment 2 George Iosif 2011-03-26 11:20:21 UTC

Ah, ok. I didn't know about the Alt+F9 behavior.
Please disregard the Firefox issue then.

Still, I believe that, when you have only one application running and you minimize that, you should not be left with an empty screen (i.e. no top panel, no action when you move the mouse in the top-left corner).
Instead, I think you should see the same behavior as when you have more than one application running and you minimize the current window (i.e. the top panel is still being displayed).

I changed the bug details to reflect this second issue, since I believe it is a Gnome problem.

Regards,
George

Comment 3 Fedora End Of Life 2013-04-03 18:53:52 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 4 Ryan Lerch 2014-12-05 15:14:46 UTC

I can't seem to recreate this issue on Fedora 20 or Fedora 21.

Are you still hitting this issue on these newer versions of Fedora?

Comment 5 George Iosif 2014-12-07 21:46:35 UTC

This issue was reported so long ago, it's become irrelevant (to me anyway).
Plus, I'm using a different desktop environment these days.
So, from my perspective, this bug can be closed.

Thanks,
George