`[xxx preload-host-spawn-strategy] Warning: waitpid override ignores groups` in the integrated terminal after first start. #370

jorchube · 2022-12-29T12:28:58Z

Hi,

The Integrated Terminal is showing these [xxx preload-host-spawn-strategy] Warning: waitpid override ignores groups warning messages for each and every command executed.

This happens in a fresh (no configuration, sync, extensions installed or defaults modification of any sort) application, except for the first start ever, after which it happens always.

Attached there is a screencast showing a first start of the application in which the issue does not happen. After closing and reopening again, the warning messages start appearing.

Screencast.from.2022-12-29.12-52-28.webm

This happens both in the default sh terminal profiles as well as in the bash ones.
These warning messages start flooding the terminal output as they also appear for any subshell spawned as part of an executed command and if the prompt executes anything, so even just pressing enter can lead to a unbearable flood of warning messages as the prompt gets resolved.

Tracking down previous commits, commit e03d4ed40326424ecd9f55e3e69afa9e6292a149c718d5da2ee35e7c5fafe38c is the first one exhibiting this issue, and downgrading to the previous one a3c1c20103d56d180dd30c5bdf25763520dbe0987e2ebadd96922ed109d66626 mitigates it.

    Commit: e03d4ed40326424ecd9f55e3e69afa9e6292a149c718d5da2ee35e7c5fafe38c
   Subject: Update 2 modules (4de6104a)
      Date: 2022-12-08 09:39:48 +0000

    Commit: a3c1c20103d56d180dd30c5bdf25763520dbe0987e2ebadd96922ed109d66626
   Subject: Update 2 modules (35102f6c)
      Date: 2022-11-09 20:14:02 +0000

On Fedora Silverblue 37, Wayland, GNOME.

I was not able to reproduce this on a non-flatpak installation.

Please let me know if there is any other information that I can provide.

The text was updated successfully, but these errors were encountered:

susantpatel · 2023-01-08T17:11:13Z

Same thing happening for me after a fresh installation of linux mint. I have installed VS code form software Manager

susantpatel · 2023-01-08T17:23:34Z

I installed it form official vs code website and the issue is gone

IkenoMike · 2023-01-10T15:38:48Z

Same issue is happening to me. I will hold out for a bit hoping that it will be fixed. If not, I will download from official vs code website.

safejace · 2023-01-23T23:19:07Z

+1 happening with the flatpak

caneserr · 2023-01-28T13:33:52Z

+1 flatpak

Toso42 · 2023-02-14T10:58:56Z

+1 flatpak

fadykuzman · 2023-04-22T17:39:34Z

+1 IntellJ Idea with flatpak on NixOs 22.11

an0pheles · 2023-04-22T21:17:00Z

+1 IntelliJ Community with flatpak on Mint Linux

pliuchkin · 2023-04-23T13:02:55Z

+1 Intellij Community with flatpak on OpenSUSE Tumbleweed.

Cpyte-Engine-Developer · 2023-05-08T08:41:24Z

+1 flatpak, PyCharm

iihmsunn · 2023-05-08T20:18:22Z

a workaround for vscode that seems to be working for me is to add these to settings.json

"terminal.integrated.defaultProfile.linux": "bash",
"terminal.integrated.profiles.linux": {
    "bash": {
        "path": "/usr/bin/flatpak-spawn",
        "args": [
            "--env=TERM=xterm-256color",
            "bash",
            //next two lines are only required if you use external sdks, edit to use yours
            "-c",
            "export PATH=$PATH:/usr/lib/sdk/dotnet7/bin:/usr/lib/sdk/node18/bin; bash"
        ]
    }
}

opravil-jan · 2023-05-10T12:43:47Z

+1 flatpak

bruno-henr · 2023-05-12T20:04:28Z

really occurred in vscode flatpak, i just download official version and solved

bruno-henr · 2023-05-12T20:06:10Z

Debian and Ubuntu based distributions
The easiest way to install Visual Studio Code for Debian/Ubuntu based distributions is to download and install the .deb package (64-bit), either through the graphical software center if it's available, or through the command line with:

sudo apt install ./.deb

jcleng · 2023-05-16T15:02:39Z

+1 IntellJ Idea with flatpak on NixOs 22.11

the same

youpie · 2023-05-25T08:21:55Z

+1 flatpak on fedora 38

DKraeff · 2023-05-25T16:46:50Z

+1 on Mint

I downloaded it from the Software Manager and it worked just fine but, at one point, it started giving me the same warning.

abhigit23 · 2023-05-25T17:09:13Z

Edited: Uncheck this setting solved the issue for me!!!

bantryblues · 2023-05-26T17:23:55Z

Edited -- reinstalled and it no longer happens
Previously it happened to me too on fedora silverblue 38 with flatpak vscode and using toolbox container

I removed the vscode flatpak and everything else installed for it for using it with toolbox. Then I used the popular script for running vscode in a container -- and it works fine now. So, something wrong when setting it up myself. I couldn't find a good description of how to do it anywhere. Here's where the script is:
https://github.com/owtaylor/toolbox-vscode

ranisalt · 2023-05-30T21:52:24Z

Edited: Uncheck this setting solved the issue for me!!!

This is the answer. The flatpak should see if it's possible to override this setting, as it comes enabled by default. Principle of most astonishment, I guess...

joelaspe · 2023-05-31T18:16:58Z

+1 for unchecking the Use Sandbox option. (came default on for me with a flatpak installation)

AlexanderTonn · 2023-06-01T10:52:43Z

+1 Linux Mint 21.1 Vera, but the issue is gone after the tip with the "deactivating Use Sandbox" Workaround (see above)

Calastrophe · 2023-06-02T02:39:11Z

Edited: Uncheck this setting solved the issue for me!!!

This fixed the issue for me. Pop OS 22.04 LTS.

dimib-tech · 2023-06-04T16:43:18Z

Edited: Uncheck this setting solved the issue for me!!!

Vanilla OS 22.10 - This fixes the issue!

ttoommxx · 2023-06-13T22:08:03Z

The option was removed and the problem is back. Any solution?

fabianmuehlberger · 2023-06-14T16:10:59Z

+1

adlermo · 2023-06-15T21:09:39Z

In Help -> About

Visual Studio Code

Version: 1.79.0
Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302
Date: 2023-06-07T14:28:44.251Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 5.10.0-23-amd64

The option Use Sandbox mentioned above is no longer available

tfrum · 2023-06-15T23:10:31Z

The option Use Sandbox mentioned above is no longer available

Confirming this is an issue for me, as well:

Version: 1.79.1
Release: 23164
Commit: 5d4b595142dd2d0a0001531e9c48b36fc795cef2
Date: 2023-06-13T18:23:51.444Z
Electron: 22.3.10
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 6.3.5-200.fc38.x86_64

Aqua1ung · 2023-06-16T19:21:43Z

The option Use Sandbox mentioned above is no longer available

Ditto.

Version: 1.79.0
Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302
Date: 2023-06-07T14:28:44.251Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 6.3.8-1321.native

islamux · 2023-08-16T04:15:35Z

I think I found a simpler workaround for Flatpak users.
The issue seems to be the LD_PRELOAD environmental variable based on a fix that was recently committed to the affected component. Since VS Code has a setting for changing environmental variables for the integrated terminals, I just needed to add the following entry to my settings.json file to unset that variable and stop the errors.
    "terminal.integrated.env.linux": {
        "LD_PRELOAD": null,
    },
No other environmental variables beyond the one entered in the setting appear to be affected, so things like $PATH or SDK-specific environmental variables should remain unchanged.
This worked for me as well.
Pop_OS 22.04 LTS, Regolith Desktop
I use VSCodium and not VSCode, still worked!
    "terminal.integrated.env.linux": {
        "LD_PRELOAD": null,
    }
Fedora 38 Flatpak

Thanks ^_^ Works for me like a charm !

I reinstaledl it based on recommendation in its site , to avoid the problem in flatpak.

ja-romar · 2023-09-01T02:44:47Z

I installed it form official vs code website and the issue is gone

I do it and it works.
Thank you so much man

PythonCoderUnicorn · 2023-09-02T02:27:58Z

I tried all of the suggestions. I uninstalled, reinstalled from flatpak and Pop! Shop. I tried changing the README settings but did not work. when i tried to paste the snippet i could not save the file.

I just uninstalled it, as no one shared where to locate this file other than the initial app load that shows README. I just wanted a code editor to work.

binuvijayan893 · 2023-09-13T12:36:06Z

Install from officel

GregLawson · 2023-09-15T14:15:14Z

I tried all of the suggestions. I uninstalled, reinstalled from flatpak and Pop! Shop. I tried changing the README settings but did not work. when i tried to paste the snippet i could not save the file.

I just uninstalled it, as no one shared where to locate this file other than the initial app load that shows README. I just wanted a code editor to work.

For those unfamiliar with editing VSCode settings.json files (I, too, was a little fuzzy while reading these comments):

In VsCode or VsCodium pick the File menu > Preferences > Settings (or control-, as a shortcut)
you should be presented with a Search settings bar,
paste into the search "terminal.integrated.env.linux" without the double quotes,
click on the "Edit in settings.json",
paste ""LD_PRELOAD": null," (again without the quotes) into the bracketed JSON expression,
Review the JSON for cut /paste errors. You should see:

"terminal.integrated.env.linux": {
"LD_PRELOAD": null,
}

Save the settings.json file,
Restart your VsCode terminal for the new settings.json to take effect.

vaibzzz123 · 2023-09-16T03:36:16Z

Did anyone get this working on Fedora 38 w/flatpak install? Still having the issues after doing the LD_PRELOAD override in the settings.json file

GregLawson · 2023-09-16T14:55:42Z

I got this working on Fedora 38 Kinoite with both the VsCode and VsCodium flatpaks.
my settings.json file is:

{
"terminal.integrated.commandsToSkipShell": [
"language-julia.interrupt"
],
"julia.symbolCacheDownload": true,
"julia.executablePath": "/var/home/greg/.juliaup/bin/julia",
"julia.enableTelemetry": true,
"terminal.integrated.env.linux": {
"LD_PRELOAD": null,
},
"files.autoSave": "onFocusChange"
}

My VsCodium version is:

Version: 1.81.1
Release: 23222
Commit: aef377c42cea6e9aea642829953104f07097abfa
Date: 2023-08-10T18:29:01.714Z
Electron: 22.3.18
ElectronBuildId: undefined
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 6.4.13-200.fc38.x86_64

bensalo · 2023-09-20T12:11:14Z

+1 flatpak vscode on fedora 38 workstation

eclipseo · 2023-09-24T08:25:23Z

I don't have the issue, do you guys have

	// Object with environment variables that will be added to the VS Code process to be used by the terminal on Linux. Set to `null` to delete the environment variable.
	"terminal.integrated.env.linux": {},

in your defaultsettings.json?

Krauzer94 · 2023-09-26T16:12:58Z

Edited: Uncheck this setting solved the issue for me!!!

This is the answer. The flatpak should see if it's possible to override this setting, as it comes enabled by default. Principle of most astonishment, I guess...

I can't find this setting on my Flatpak VS Code

rtweaf · 2023-10-06T15:58:15Z

Same issue on PopOS - flatpak.

ehmad11 · 2023-10-07T18:50:41Z

I tried all of the suggestions. I uninstalled, reinstalled from flatpak and Pop! Shop. I tried changing the README settings but did not work. when i tried to paste the snippet i could not save the file.

I just uninstalled it, as no one shared where to locate this file other than the initial app load that shows README. I just wanted a code editor to work.

For those unfamiliar with editing VSCode settings.json files (I, too, was a little fuzzy while reading these comments):

In VsCode or VsCodium pick the File menu > Preferences > Settings (or control-, as a shortcut)
you should be presented with a Search settings bar,

paste into the search "terminal.integrated.env.linux" without the double quotes,

click on the "Edit in settings.json",

paste ""LD_PRELOAD": null," (again without the quotes) into the bracketed JSON expression,

Review the JSON for cut /paste errors. You should see:

"terminal.integrated.env.linux": {
"LD_PRELOAD": null,
}

Save the settings.json file,

Restart your VsCode terminal for the new settings.json to take effect.

Thank you @brianpgordon and @GregLawson, it worked for me on Fedora 38.

SeLub · 2023-10-24T11:46:45Z

Same issue on PopOS - flatpak. Solved by adding to the settings.json:

"terminal.integrated.env.linux": {
"LD_PRELOAD": null,
},

brieucdlf · 2023-10-27T16:53:43Z

Thanks @iihmsunn for the tips :) Same issue on PopOS.

vendkura · 2023-11-12T07:48:06Z

I installed it form official vs code website and the issue is gone

It works for me too (I am on Debian 12)

isikhi · 2023-11-16T09:39:37Z

Same issue LD_PRELOAD worked for me.

    "terminal.integrated.env.linux": {
        "LD_PRELOAD": null,
    }

islammohayminul · 2023-12-03T06:49:29Z

After installing from the official site, it works for me on Fedora.

shubhxg · 2023-12-05T19:06:34Z

Happened with me as well so I uninstalled it using flatpak uninstall com.visualstudio.code

and installed debian package from official website and now it works fine.

iamWing · 2023-12-16T16:17:40Z

Same issue LD_PRELOAD worked for me.

    "terminal.integrated.env.linux": {
        "LD_PRELOAD": null,
    }

This fixed the issue for me on Steam Deck using the flatpak version. Thanks.

gitsoft · 2024-01-02T19:20:49Z

Solution on POP OS 22.04

Open Pop!_Shop
Find Visual Studio Code
Uninstall
Go to https://code.visualstudio.com/download
Download latest .deb package for your CPU architecture
cd to folder where you keep downloaded files
sudo dpkg -i code_1.85.1-1702462158_amd64.deb

please note: the filename will most likely be different for you.

kalwhyte · 2024-01-07T09:06:29Z

I installed it form official vs code website and the issue is gone

This was a simple and direct fix

Thank You

AndreiSva · 2024-01-08T20:32:27Z

installing it from the vscode website is not a real fix. Is it possible to fix this in the flatpak by default?

AndreiSva · 2024-01-08T21:23:36Z

I think I found a simpler workaround for Flatpak users.

The issue seems to be the LD_PRELOAD environmental variable based on a fix that was recently committed to the affected component. Since VS Code has a setting for changing environmental variables for the integrated terminals, I just needed to add the following entry to my settings.json file to unset that variable and stop the errors.
    "terminal.integrated.env.linux": {
        "LD_PRELOAD": null,
    },
No other environmental variables beyond the one entered in the setting appear to be affected, so things like $PATH or SDK-specific environmental variables should remain unchanged.

would it be possible to build this fix into the flatpak?

Mateusinbessa · 2024-01-17T01:04:55Z

I think I found a simpler workaround for Flatpak users.

The issue seems to be the LD_PRELOAD environmental variable based on a fix that was recently committed to the affected component. Since VS Code has a setting for changing environmental variables for the integrated terminals, I just needed to add the following entry to my settings.json file to unset that variable and stop the errors.
    "terminal.integrated.env.linux": {
        "LD_PRELOAD": null,
    },
No other environmental variables beyond the one entered in the setting appear to be affected, so things like $PATH or SDK-specific environmental variables should remain unchanged.

Ubuntu 22.04
Thx! It worked for me!

christopolise · 2024-02-07T16:54:47Z

a workaround for vscode that seems to be working for me is to add these to settings.json

"terminal.integrated.defaultProfile.linux": "bash",
"terminal.integrated.profiles.linux": {
    "bash": {
        "path": "/usr/bin/flatpak-spawn",
        "args": [
            "--env=TERM=xterm-256color",
            "bash",
            //next two lines are only required if you use external sdks, edit to use yours
            "-c",
            "export PATH=$PATH:/usr/lib/sdk/dotnet7/bin:/usr/lib/sdk/node18/bin; bash"
        ]
    }
}

I was having an issue just dropping in zsh as a replacement and found out that I needed to add the --host option to the args list to make it work. Hopes this saves someone some time:

"terminal.integrated.defaultProfile.linux": "zsh",
"terminal.integrated.profiles.linux": {
        "zsh": {
            "path": "/usr/bin/flatpak-spawn",
            "args": [
                "--host",
                "--env=TERM=xterm-256color",
                "zsh",
                //next two lines are only required if you use external sdks, edit to use yours
                // "-c",
                // "export PATH=$PATH:/usr/lib/sdk/dotnet7/bin:/usr/lib/sdk/node18/bin; bash"
            ]
        }
    }

rakibweb0 · 2024-02-24T04:17:17Z

Same issue on PopOS - flatpak. Solved by adding to the settings.json:

"terminal.integrated.env.linux": { "LD_PRELOAD": null, },

It's working....

abhigit23 mentioned this issue Jun 1, 2023

waitpid override ignores groups #404

Open

paddy-exe mentioned this issue Aug 18, 2023

After following the Documentation: compiling GDExtension in VS Code results in: "scons: command not found" godotengine/godot-docs#7801

Closed

eclipseo mentioned this issue Sep 24, 2023

Does not work properly when used within Visual Studio Code 1player/host-spawn#29

Closed

alexojegu mentioned this issue Jan 27, 2024

Update zypak to 2024.01.17 #487

Merged

bilelmoussaoui closed this as completed in #487 Feb 25, 2024

[xxx preload-host-spawn-strategy] Warning: waitpid override ignores groups in the integrated terminal after first start. #370

[xxx preload-host-spawn-strategy] Warning: waitpid override ignores groups in the integrated terminal after first start. #370

Comments

jorchube commented Dec 29, 2022 • edited Loading

susantpatel commented Jan 8, 2023

susantpatel commented Jan 8, 2023

IkenoMike commented Jan 10, 2023 • edited Loading

safejace commented Jan 23, 2023

caneserr commented Jan 28, 2023

Toso42 commented Feb 14, 2023

fadykuzman commented Apr 22, 2023 • edited Loading

an0pheles commented Apr 22, 2023

pliuchkin commented Apr 23, 2023

Cpyte-Engine-Developer commented May 8, 2023

iihmsunn commented May 8, 2023

opravil-jan commented May 10, 2023

bruno-henr commented May 12, 2023

bruno-henr commented May 12, 2023

jcleng commented May 16, 2023

youpie commented May 25, 2023

DKraeff commented May 25, 2023

abhigit23 commented May 25, 2023 • edited Loading

bantryblues commented May 26, 2023 • edited Loading

ranisalt commented May 30, 2023

joelaspe commented May 31, 2023

AlexanderTonn commented Jun 1, 2023 • edited Loading

Calastrophe commented Jun 2, 2023

dimib-tech commented Jun 4, 2023

ttoommxx commented Jun 13, 2023

fabianmuehlberger commented Jun 14, 2023

adlermo commented Jun 15, 2023

tfrum commented Jun 15, 2023

Aqua1ung commented Jun 16, 2023

islamux commented Aug 16, 2023

ja-romar commented Sep 1, 2023

PythonCoderUnicorn commented Sep 2, 2023

binuvijayan893 commented Sep 13, 2023

GregLawson commented Sep 15, 2023 • edited Loading

vaibzzz123 commented Sep 16, 2023 • edited Loading

GregLawson commented Sep 16, 2023 • edited Loading

bensalo commented Sep 20, 2023

eclipseo commented Sep 24, 2023

Krauzer94 commented Sep 26, 2023

rtweaf commented Oct 6, 2023

ehmad11 commented Oct 7, 2023 • edited Loading

SeLub commented Oct 24, 2023

brieucdlf commented Oct 27, 2023

vendkura commented Nov 12, 2023 • edited Loading

isikhi commented Nov 16, 2023

islammohayminul commented Dec 3, 2023

shubhxg commented Dec 5, 2023 • edited Loading

iamWing commented Dec 16, 2023

gitsoft commented Jan 2, 2024

kalwhyte commented Jan 7, 2024

AndreiSva commented Jan 8, 2024 • edited Loading

AndreiSva commented Jan 8, 2024

Mateusinbessa commented Jan 17, 2024

christopolise commented Feb 7, 2024

rakibweb0 commented Feb 24, 2024

`[xxx preload-host-spawn-strategy] Warning: waitpid override ignores groups` in the integrated terminal after first start. #370

`[xxx preload-host-spawn-strategy] Warning: waitpid override ignores groups` in the integrated terminal after first start. #370

jorchube commented Dec 29, 2022 •

edited

Loading

IkenoMike commented Jan 10, 2023 •

edited

Loading

fadykuzman commented Apr 22, 2023 •

edited

Loading

abhigit23 commented May 25, 2023 •

edited

Loading

bantryblues commented May 26, 2023 •

edited

Loading

AlexanderTonn commented Jun 1, 2023 •

edited

Loading

GregLawson commented Sep 15, 2023 •

edited

Loading

vaibzzz123 commented Sep 16, 2023 •

edited

Loading

GregLawson commented Sep 16, 2023 •

edited

Loading

ehmad11 commented Oct 7, 2023 •

edited

Loading

vendkura commented Nov 12, 2023 •

edited

Loading

shubhxg commented Dec 5, 2023 •

edited

Loading

AndreiSva commented Jan 8, 2024 •

edited

Loading