Skip to content

Python env tool (pet) does not launch due to missing execute permissions #25500

Closed as not planned

Description

@GeraldTgl

Type: Bug

Behaviour

Pylance not activated, Python Issue reporter not launched

exthost.log shows
2025-10-02 12:49:20.755 [error] Error: spawn /home/user-id/.vscode/extensions/ms-python.python-2025.14.0-linux-x64/python-env-tools/bin/pet EACCES

Doing a 'ls -al' shows that the execute permission is missing:
-rw-r--r--. 1 geraldtgl geraldtgl 15874240 Oct 2 12:49 ms-python.python-2025.14.0-linux-x64/python-env-tools/bin/pet

Doing a 'chmod +x ms-python.python-2025.14.0-linux-x64/python-env-tools/bin/pet' fixes the problem.

Regression of #23677 ?

Diagnostic data

Extension version: 2025.14.0
VS Code version: Code 1.104.2 (e3a5acfb517a443235981655413d566533107e92, 2025-09-24T11:21:37.073Z)
OS version: Linux x64 4.18.0-553.71.1.el8_10.x86_64
Modes:

  • Python version (& distribution if applicable, e.g. Anaconda): 3.13.1
  • Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Unknown
  • Value of the python.languageServer setting: Default
Installed Extensions
Extension Name Extension Id Version
js-debug ms- 1.104.0
js-debug-companion ms- 1.1.3
python ms- 2025.14.0
vscode-js-profile-table ms- 1.0.10
System Info
Item Value
CPUs AMD EPYC 9455 48-Core Processor (8 x 0)
GPU Status 2d_canvas: unavailable_software
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
webnn: unavailable_software
Load (avg) 0, 0, 0
Memory (System) 31.11GB (22.88GB free)
Process Argv . --crash-reporter-id 2776c536-5f90-434c-9342-a35bffac0821
Screen Reader no
VM 100%
DESKTOP_SESSION gnome
XDG_CURRENT_DESKTOP GNOME
XDG_SESSION_DESKTOP gnome
XDG_SESSION_TYPE x11

Activity

  1. eleanorjboyd commented on Oct 3, 2025

    @eleanorjboyd
    Member

    Karthik Nadig (@karthiknadig) it should have the correct permissions when we create it right? What user permissions do we check and setup the executable using?

  2. GeraldTgl commented on Oct 6, 2025

    @GeraldTgl
    Author

    I would expect the execute permission is added during build looking at the following lines but somehow it seems this step is not running anymore?

    chmod +x ./python-env-tools/bin/pet*

    chmod +x ./python-env-tools/bin/pet*

  3. eleanorjboyd commented on Dec 12, 2025

    @eleanorjboyd
    Member

    Don Jayamanne (@DonJayamanne) do you know if this is something on the PET side?

  4. DonJayamanne commented on Jan 5, 2026

    @DonJayamanne

    There's nothing that needs to happen on PET side, PET will only create the executable.
    Setting permissions (if required) needs to be done by Python (or other extensions) that distribute PET

    chmod +x ./python-env-tools/bin/pet*

    Also changing permissions in builds is not going to work, as these permissions are applicable ONLY for the machine on which chmod was executed on.

    Feels like something else is going on, else every user should be running into this issue.

  5. eleanorjboyd commented on Jan 5, 2026

    @eleanorjboyd
    Member

    hm its a good point. GeraldTgl are you on a remote machine with stricter settings or maybe a enterprise managed machine? Worth determining what about your setup would cause this problem to arise for only you

  6. github-actions commented on Feb 5, 2026

    @github-actions

    Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

    Happy Coding!

  7. GeraldTgl commented on Feb 5, 2026

    @GeraldTgl
    Author

    Apologies for the delay. This happened on RHEL 8 VMs that are enterprise managed through Puppet. Multiple users reported this issue and I was able to reproduce it at the time. In the mean time I do not work for this customer anymore and don't have access to their systems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

triage-neededNeeds assignment to the proper sub-team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions