Menu bar in second window

[jsaffer]

Type: Bug

Hello! When I open a second Window in VS Code, I cannot use the menu bar at the top. Clicking on "File" or "Terminal" doesn't show me the menu any more. It only works when there is only one window opened.

VS Code version: Code 1.71.0 (784b017, 2022-09-01T07:25:10.472Z)
OS version: Linux x64 5.15.0-46-generic
Modes:
Sandboxed: No
Remote OS version: Linux x64 4.19.246

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1500)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: disabled_software video_encode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	2, 2, 1
Memory (System)	15.16GB (9.53GB free)
Process Argv	--unity-launch --crash-reporter-id 5597d512-2f79-4acf-84a9-ddcd8c94b20a
Screen Reader	no
VM	0%
DESKTOP_SESSION	ubuntu
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	ubuntu
XDG_SESSION_TYPE	x11

Item	Value
Remote	SSH: cobalt06
OS	Linux x64 4.19.246
CPUs	Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz (32 x 1299)
Memory (System)	62.86GB (38.50GB free)
VM	0%

Extensions (9)

Extension	Author (truncated)	Version
jupyter-keymap	ms-	1.0.0
remote-ssh	ms-	0.84.0
remote-ssh-edit	ms-	0.80.0
rainbow-csv	mec	2.4.0
python	ms-	2022.14.0
vscode-pylance	ms-	2022.8.50
jupyter	ms-	2022.8.1002431955
jupyter-keymap	ms-	1.0.0
jupyter-renderers	ms-	1.0.9

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30557515
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
pylanb8912:30545647
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012:30540252
azure-dev_surveyonecf:30548226
i497e931:30553904

[bmewburn]

I'm experiencing this too.

1. Open vscode which loads previous folder.
2. File -> New Window.
3. Maximize the new window.
4. Click File. It may open first time but subsequent clicks fail to open it. At times it flashes briefly.
5. Switch back to previous window and click File. It works.
6. Now go back to new window and click File. It works again.

Version: 1.71.0
Commit: 784b017
Date: 2022-09-01T07:25:10.472Z
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Linux x64 4.19.0-21-amd64
Sandboxed: No

[danwdart]

Additionally, this only happens for me when I don't wait some time for the window to invisibly load (a few seconds). After this time it's fine.

[rzhao271]

I notice on Ubuntu that the file menu often closes itself when one has it open for a while, and I think it has to do with some parts of the program delaying when they load in these days. I can't reproduce the case where the menu doesn't show at all, though.
@jsaffer @bmewburn is the menu entirely not working for you two still on the latest Insiders?

[bmewburn]

@rzhao271 I just did a fresh install of insiders and it still happens for me when I follow the steps in my comment above quickly. I've noticed that if I wait an extended period of time (~30s) before maximising the new window then it works fine, as does loading a folder in the new window before maximising.

[deepak1556]

@bmewburn can you clarify the following points as well,

1. Are you using "window.titleBarStyle": "custom" or the default native ?
2. Are you running on X11 or Wayland ? If Wayland, are you running with --ozone-platform=wayland --enable-features=WaylandWindowDecorations ?

[bmewburn]

@deepak1556

1 . I'm using native. Switching to custom solves my issue but at first glance I prefer not to use it because it's hard to distinguish a new window on top of the previous window because of lack of border/shadow.
2. Wayland. Passing those flags causes a bunch of other issues like not being able to maximise or drag/drop new window.

[deepak1556]

Thanks for confirming, it is recommended to run with native wayland support in the runtime. The issues you mentioned are tracked in #156723 and #168620, which will be addressed with next runtime update. Can you follow those issues for updates, thanks!

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[danwdart]

I haven't seen this recently, it seems to be better on 1.74.1, perhaps.