[Linux] Open file or Open folder creates dialog behind active window

[kathenas]

Native dialogs Open file or Open folder opening behind main window on RHEL 8/EL 8 clones.

This has only happened after updating to 1.66.0.

Desktop Environment: gnome.

Screencast.from.31-03-22.12.32.59.mp4

[EvgeniyMakhmudov]

The same problem on Linux Mint with Mate env after update to 1.66. I hope that will be fixed in 1.66.1 but it is not.

[jherico]

Same behavior on Ubuntu 22.04 pre-release, but I was also seeing it on 20.04 before I upgraded yesterday.

Visual Studio Code

"Open File" is ready

and then I can get to the dialog by clicking on the toast or by using the switch-window shortcut key.

Code About dialog output

Version: 1.66.2
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-11T07:49:24.808Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Linux x64 5.15.0-25-generic

[bradym]

Seeing the same issue, I didn't find this ticket so I filed #147400 which I have now closed as a duplicate of this one. Mentioning here in case there's anything useful on that ticket when this one gets worked on.

[carneeki]

Also happening to me on Arch Linux with GNOME 42 under Wayland:

Help -> About as follows:

Version: 1.66.2
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-11T07:49:24.808Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Linux x64 5.17.3-arch1-1

[gregersn]

Same issue, Ubuntu 21.10, Cinnamon VM.

Version: 1.66.2
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-11T07:49:24.808Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Linux x64 5.13.0-39-generic

[ghost]

Same issue on Arch Linux running VSCodium on Cinnamon.

Version: 1.66.2
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-13T00:16:29.523Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Linux x64 5.17.4-zen1-1-zen

[kozhukalov]

Same for me

Version: 1.66.2
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-11T07:49:24.808Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Linux x64 5.17.4-100.fc34.x86_64

[KollegeX]

Here as well

Version: 1.66.0
Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5
Date: 2022-04-02T14:00:30.308Z
Electron: 17.3.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.15.32-1-MANJARO

[embeddedt]

Same issue using Arch and KDE Plasma.

Version: 1.66.0
Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5
Date: 2022-04-02T14:00:30.308Z
Electron: 17.4.0
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.17.4-arch1-1

Operating System: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.4-arch1-1 (64-bit)
Graphics Platform: X11

[astrolemonade]

Same issue here using Solus Linux 4.1

Version: 1.67.0
Commit: 57fd6d0195bb9b9d1b49f6da5db789060795de47
Date: 2022-05-06T09:53:29+10:00
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.15.37-214.current

[wc7086]

Same issue using Arch and KDE Plasma(Wayland).
But, this error does not appear when opening it for the first time. (Delete all configuration files or reboot the system and open vscode for the first time)
@deepak1556

Version: 1.67.1
Commit: da15b6fd3ef856477bf6f4fb29ba1b7af717770d
Date: 2022-05-10T21:35:59.370Z
Electron: 17.4.3
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.17.7-arch1-1

[AlbanMinassian]

Same problem ubuntu 20 or 22:

code (v1.67.1)
first open dialog: right place
second et other open dialog: always behind application

sudo apt ugrade (code 1.67.1 to 1.67.2)
code
first open dialog: right place
second et other open dialog: always behind application

[SethBashamDev]

Currently have this issue with Save As. Running Fedora 36 Workstation.

VS Code installed via Microsoft repo not Snap/FlatPak

[eksperimental]

Currently have this issue with Save As. Running Fedora 36 Workstation.

VS Code installed via Microsoft repo not Snap/FlatPak

Seems like a temporary solution

[toasterofbread]

Currently have this issue with Save As. Running Fedora 36 Workstation.
VS Code installed via Microsoft repo not Snap/FlatPak

Seems like a temporary solution

I think they were just mentioning the setup they experienced the issue with, not suggesting it as a solution.

[eksperimental]

Currently have this issue with Save As. Running Fedora 36 Workstation.
VS Code installed via Microsoft repo not Snap/FlatPak

Seems like a temporary solution

I think they were just mentioning the setup they experienced the issue with, not suggesting it as a solution.

That's why I say "temporary".

[toasterofbread]

That's why I say "temporary".

I mean that it's not a solution at all, just that they experienced the bug using the MS repo version.

[eksperimental]

That's why I say "temporary".

I mean that it's not a solution at all, just that they experienced the bug using the MS repo version.

It is a temporary solution for those who need to use the editor today.

[kathenas]

That's why I say "temporary".

I mean that it's not a solution at all, just that they experienced the bug using the MS repo version.

It is a temporary solution for those who need to use the editor today.

@SethBashamDev is stating they have the issue and that the version they are using is installed from the MS RPM repo. There is no mention of a temporary solution. Please refrain from adding noise to this bug report.

[kathenas]

On Tue, 2022-07-05 at 23:58 -0700, JulienBERNU wrote: Had the same issue... until I restarted VSCode. Now it's behaving. Worth a try... :) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

If you stated install source, platform etc. this comment may have some use. But the issue remains and your comment is not helpful. Regards Phil

…

-- *** Playing the game for the games own sake. *** Associations: * Debian Maintainer (DM) * Fedora/EPEL Maintainer. * Contributor member of the AlmaLinux foundation. WWW: https://kathenas.org Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg Twitter: @kathenasorg Instagram: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B

[ecm75]

This above mentioned workaround works for me on Debian 11 not using Wayland:
GTK_USE_PORTAL=0 code

Version: 1.68.1
Commit: 30d9c6cd9483b2cc586687151bcbcd635f373630
Date: 2022-06-15T02:58:26.441Z
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.10.0-14-amd64

[ogrand]

Same issue with latest code release (open dialog is behind vscode window).

Version: 1.69.1
Commit: b06ae3b
Date: 2022-07-12T08:28:29.328Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Linux x64 5.4.0-122-generic

Workaround GTK_USE_PORTAL=0 code doesn't fix.

Regards

[phamphu232]

Same issue

Version: 1.69.1
Commit: b06ae3b
Date: 2022-07-12T08:28:29.328Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Linux x64 5.4.0-121-generic

[Rayv1]

same

Version: 1.69.1
Commit: b06ae3b
Date: 2022-07-12T08:28:29.328Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Linux x64 5.13.0-52-generic snap

[deepak1556]

Thanks everyone for the inputs, at this time we know the root cause of the issue in upstream. I am going to lock this issue to avoid some noise. I will reopen the issue once a fix has been made.