Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Panel appears over fullscreen windows when switching workspaces #4404

Closed
Archenoth opened this issue Jul 6, 2015 · 4 comments
Closed

Panel appears over fullscreen windows when switching workspaces #4404

Archenoth opened this issue Jul 6, 2015 · 4 comments

Comments

@Archenoth
Copy link

Archenoth commented Jul 6, 2015

When a window is fullscreen on a workspace, the panel is hidden below the window. This is good.
When you switch workspaces, and switch back, it remains hidden. This is also good.
But, when you try this with two monitors, the panel appears above the fullscreen window. This is not.

You can see the panel is blocking the Emacs Modeline on my first monitor here:
screenshot from 2015-07-06 09 59 24

This happens reliably every workspace switch, and it happens regardless of the contents of the second monitor. (So, it happens when the fullscreen application is the only thing open.)

You can fix it by unfocusing the window... (Which seems to inadvertently happen when taking a screenshot.)

This is with Cinnamon version 2.6.11+rafaela.

@Archenoth
Copy link
Author

As a bit of an update... The workaround to hide the menubar I mentioned above does not appear to work when the fullscreen window is the only window open on any workspace.

Instead, you have to take the window out of fullscreen and put it back in again.

(Checked with 2.6.13)

@Archenoth Archenoth changed the title Panel appears over fullscreen windows when switching workspaces -- only when multiple monitors are plugged in. Panel appears over fullscreen windows when switching workspaces Jul 9, 2015
@Archenoth
Copy link
Author

I also found out that [Ctrl] + [Backspace] works as another workaround. (I wonder why those two keys in particular?)

@Archenoth
Copy link
Author

Since this is mildly infuriating, and because the key-combo workarounds fail now... Here is what I use as an Emacs hook to keep it in the foreground.

(add-hook 'focus-in-hook (lambda ()
                           (lower-frame)
                           (raise-frame)))

While this is application-specific, it probably gives a hint as to what is wrong... (Since I am just unfocusing and focusing in the frame again)

@JosephMcc
Copy link
Contributor

Should be fixed by #5229

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants