I get a black screen, from time to time, in vscode. I can still see the minimize and restore/maximize buttons on the top right of the window. If I click them, I can see the contents of vscode again. Then I leave vscode untouched for a few minutes and the contents go black again...
Has anyone experienced this? It doesn't crash, it's just the contents that turn black.
I'm using Gnome 49, wayland. And this vscode package from AUR. My GPU is:
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 33 [Radeon RX 7600/7600 XT/7600M XT/7600S/7700S / PRO W7600] (rev c0)
Pinned Comments
dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2025-09-24 09:46 (UTC) by dcelasun)
FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)
This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the licence difference and branding, there are some proprietary features not available in the open-source version.
Please check this page before flagging as out-of-date. If there is no new version on that page, it's not yet released. A tag on GitHub is NOT a release! If you can see the new version on the updates page, but the AUR package is still not updated, flag it and give it time. It's usually done within hours.
Sometimes AUR helpers do weird things. Download the tarball and install it manually with
makepkg -si. If that works, report the problem to your AUR helper's upstream, not here.xdg-openuses vscode, not my file manager! How do I fix this?Install
shared-mime-info-gnomegnome-sessionwhich now includes mimemapps.Just because $X is not required to open the app, doesn't mean there is nothing that depends on it. Always search the comment history on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap to make sure it's really not needed. If namcap doesn't complain, please leave a comment here and I'll investigate.
The problem might be a packaging issue (wrong paths, dependencies, icons), so please write a comment here first. If you don't get a reply, or if someone says it's an upstream issue, you can report it on GitHub.
No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.