Menus open behind application window

[ghost]

Prerequisites

• [Y] Can you reproduce the problem in safe mode?
• [Y] Are you running the latest version of Atom?
• [Y] Did you check the debugging guide?
• [Y] Did you check the FAQs on Discuss?
• [Y] Are you reporting to the correct repository?
• [Y] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.

Description

Atom menus (File, Edit etc) open behind the application window.

Steps to Reproduce

1. Fullscreen the window
2. Open a menu

Expected behavior: See the displayed menu

Actual behavior: Menu gets obscured by the application window

Versions

You can get this information from executing atom --version and apm --version at the command line. Also, please include the OS and what version of the OS you're running.

Atom : 1.7.2
Electron: 0.36.8
Chrome : 47.0.2526.110
Node : 5.1.1
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial

Both Ubuntu and Atom are fresh installs using the latest builds.

[Flos]

I can confirm the bug on a fresh installed Ubuntu 14.04 LTS, makes it unusable for me!
The title bar is acting normal, the Atom content window stays always on top.

Atom : 1.7.2
Electron: 0.36.8
Chrome : 47.0.2526.110
Node : 5.1.1

apm 1.9.2
npm 2.13.3
node 0.10.40
python 2.7.6
git 1.9.1

[50Wliu]

Can not reproduce on Ubuntu 16.04, Atom 1.9.0-dev-9175194.

[lee-dohm]

@ashlynblack or @Flos Can you reproduce this behavior using Chromium?

[Flos]

@lee-dohm
google-chrome is not installed, only the chromium-browser. If its integrated in the Atom package, I have no clue how to change the browser. I see no cli option for that.

But I just looked a bit deeper in it. I started the chromium-browser using the terminal and got a error and a messed up webview, looked a bit like many broken textures. The error pointed me to a recent, Virtualbox 3D acceleration issue: http://permalink.gmane.org/gmane.comp.emulators.virtualbox.user/6225

Now I disabled 3D acceleration in my VM and the chromium-browser is working fine, and also Atom.

I think it's an Virtualbox 3D driver bug not a Atom bug at all.
Thanks for the support!

[lee-dohm]

Glad to hear it is working for you @Flos. Any updates from you @ashlynblack?

[isapa1984]

I was having this same issue on Debian Jessie using Virtual Box 5.0.20 with 3d Acceleration on. Disabling 3D did the trick. This problem wasn't happening until version 5.0.16.

UPDATE: After research, I discovered that this problem is caused by the versions of guest additions that came after 5.0.16. If you use Virtual Box 5.0.20 but using Guest Additions 5.0.16 instead, this issue doesn't occur. Tested and confirmed.

[Nikki1993]

Confirming same behaviour in VBox as others. Getting rid of 3D acceleration or downgrading guest additions resolves issue with Atom editor.

[hoto]

For a Vagrant/VirtualBox powered GUI machine workaround is to write this to Vagrantfile

vb.customize ["modifyvm", :id, "--accelerate3d", "off"]

[lee-dohm]

Since there is no response from @ashlynblack and it seems everyone else is having luck with either using a different version of guest additions or turning off 3D acceleration, I'm going to close this as resolved. Thanks everyone!

[draeath]

That's... that's not really a fix, just a (bad) workaround.

Assuming the atom (chromium?) code is fine (pretty sure it is). Has anyone opened a bug with Oracle?

EDIT: Well, that's a good sign. This bug was opened 2 years ago and is still in state "new defect."

Though, apparently setting an environment variable within the guest works:

Setting LIBGL_ALWAYS_SOFTWARE=1 solved this problem for me

I'm not familiar with the ramifications of setting this variable. Is this effectively disabling hardware accelerated OpenGL, albeit in a much more granular fashion?

[dazza-codes]

Reproduced this issue, see related comment in

• Atom menus in ubuntu 13.10 are cut off or don't show #1959 (comment)

Confirmed that atom is OK with 3D acceleration on Virtual Box 5.0.20, using Guest Additions 5.0.16. Installed the guest additions from a manual download and install from http://download.virtualbox.org/virtualbox/5.0.16/VBoxGuestAdditions_5.0.16.iso

[jrial]

In case anyone's interested, the VirtualBox guys have a wiki page describing the current situation: https://www.virtualbox.org/wiki/X11Guest3D

Unfortunately, it appears they lack the manpower to tackle this, and are counting on the community to provide patches. Needless to say, that hasn't happened yet.

I can confirm I still get the black screen permanently on top with VirtualBox 5.1.8, regardless of whether I install the matching guest additions or the 5.0.16 ones.

[KUGA2]

The same issue occurs with qtcreator welcome screen. 5.0.16 fixes it, but also disables 3D hardware accelleration. You can see this, because the "Unity Start Menu" is loading a lot slower.

[ichiriac]

You can also disable GPU only on atom application by creating a shortcut on the desktop and adding --disable-gpu argument to the application.

It's fixing the problem on atom and I still use 3d acceleration on ubuntu (works with any electron based application)

[draeath]

That's much more convenient than defining LIBGL_ALWAYS_SOFTWARE=1 in the environment. Good find!

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!