vscode: Integrated terminal fails to launch: execvp(3) failed.: Permission denied

We have written the needed data into your clipboard because it was too large to send. Please paste. Issue Type: Bug

When I try to open a new integrated terminal (bash) the terminal process fails to launch with error:

execvp(3) failed.: Permission denied

VS Code version: Code - Insiders 1.57.0-insider (4f3d865a6b46a4ead49cf83fe1c30d95d0a34220, 2021-05-31T05:13:16.692Z) OS version: Linux x64 4.15.0-143-generic

System Info

Item	Value
CPUs	Intel® Xeon® CPU E5-2620 0 @ 2.00GHz (24 x 1249)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	1, 1, 1
Memory (System)	31.34GB (5.32GB free)
Process Argv	–disable-extensions --crash-reporter-id a8517064-3fb8-42aa-bb9b-19f723e00b1c
Screen Reader	no
VM	0%
DESKTOP_SESSION	unity
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	unity
XDG_SESSION_TYPE	x11

Extensions disabled

A/B Experiments

vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
vsc_aacf:30263846
vspre833cf:30267465
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscus158:30286553
pythonvsuse255:30303025
vscgsv2:30305091
vscorehov:30301224
vscod805:30301674
vscextlang:30310088

About this issue

Original URL
State: open
Created 3 years ago
Reactions: 5
Comments: 26 (8 by maintainers)

Most upvoted comments

This comment is revealing:

https://github.com/microsoft/vscode/issues/126017#issuecomment-861379341

FWIW - adding the following setting fixed things for me:
    "terminal.integrated.profiles.linux": {
        "bash": {
            "path": "/bin/bash"
        },

    },
Which by default just points to bash - without a path.

Happens on macOS and Linux, assigning to June if we have time to investigate.

+13

Tyriar on Jun 29, 2021

This comment is revealing: #126017 (comment) FWIW - adding the following setting fixed things for me:
    "terminal.integrated.profiles.linux": {
        "bash": {
            "path": "/bin/bash"
        },

    },
This helped me resolve the issue with the following variation
"terminal.integrated.profiles.osx": {
        "zsh": {
            "path": "/bin/zsh"
        },
    },

works for me

hustzyd on Oct 8, 2021

I’ve been running into this a long time, and <knock on wood> I fixed it by running which zsh in an external terminal, and pasting the result of that into the settings, ala "terminal.integrated.profiles.osx": { "zsh": { "path": "/usr/local/bin/zsh" }, },

mckethanor on Sep 29, 2021

This comment is revealing:

#126017 (comment)

FWIW - adding the following setting fixed things for me:
    "terminal.integrated.profiles.linux": {
        "bash": {
            "path": "/bin/bash"
        },

    },

This helped me resolve the issue with the following variation

"terminal.integrated.profiles.osx": {
        "zsh": {
            "path": "/bin/zsh"
        },
    },

kevnm67 on Sep 21, 2021