Repository navigation
Remote (SSH) debugging/running not working on python files #25670
Description
Type: Bug
Opening a python project folder in VSCode from pi via SSH.
The VS code is already setup to run the python current open file when pressing F5 or the play button to run in debug mode. But I think after the recent update something is not working right. Pressing the play button is not doing any actions. In Some wried times the play button works. If i restart the VSCode, it may work.. weird things happening..
VS Code version: Code 1.103.1 (360a4e4fd251bfce169a4ddf857c7d25d1ad40da, 2025-08-12T16:25:40.542Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux arm 6.1.21-v8+
System Info
| Item | Value |
|---|---|
| CPUs | 12th Gen Intel(R) Core(TM) i7-12800H (20 x 2803) |
| GPU Status | 2d_canvas: enabled 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_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 31.68GB (6.79GB free) |
| Process Argv | --crash-reporter-id 69884d51-6ecb-4ec3-9fcf-e7441fa89780 |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | SSH: 192.168.0.102 |
| OS | Linux arm 6.1.21-v8+ |
| CPUs | unknown (4 x 1500) |
| Memory (System) | 3.70GB (2.35GB free) |
| VM | 0% |
Extensions (18)
| Extension | Author (truncated) | Version |
|---|---|---|
| vsc-python-indent | Kev | 1.21.0 |
| jupyter-keymap | ms- | 1.1.2 |
| remote-containers | ms- | 0.422.1 |
| remote-ssh | ms- | 0.120.0 |
| remote-ssh-edit | ms- | 0.87.0 |
| remote-wsl | ms- | 0.99.0 |
| vscode-remote-extensionpack | ms- | 0.26.0 |
| remote-explorer | ms- | 0.5.0 |
| remote-server | ms- | 1.5.2 |
| vscode-serial-monitor | ms- | 0.13.1 |
| jinja | who | 0.0.8 |
| copilot | Git | 1.350.0 |
| copilot-chat | Git | 0.30.1 |
| debugpy | ms- | 2025.11.2025072901 |
| python | ms- | 2025.13.2025081501 |
| vscode-pylance | ms- | 2025.7.102 |
| sqlite-viewer | qwt | 0.10.6 |
| bash-debug | rog | 0.3.9 |
A/B Experiments
vsliv368cf:30146710
binariesv615:30325510
aa-v8-r5-etc:31366715
nativeloc1:31344060
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
747dc170:31275177
aj953862:31281341
pylancequickfixf:31358881
9d2cg352:31346308
convertlamdaf:31358879
usemarketplace:31343026
nesew2to5:31336538
agentclaude:31335814
replacestringexc:31350595
nes-set-on:31340697
6abeh943:31336334
envsdeactivate2:31353495
yijiwantestdri0626-c:31336931
0927b901:31350571
ji9b5146:31348712
45650338:31358607
0cj2b977:31352657
controlchatstate:31363048
pylancealldocst:31367567
gemagent1cf:31368470
retrydisabled:31368125
Activity
tojiamathewwork commentedon Aug 18, 2025
I kill all python process, including python and python3 on the pi, to make sure no python process are running on the pi, before running the python process from vscode on windows (via ssh), then mostly this issue happens.
The "Developer: Reload Window" option (under View > Command Palette..) helps me to fix this issue.
eleanorjboyd commentedon Dec 9, 2025
Hi! Are you still seeing this problem?
tojiamathewwork commentedon Dec 9, 2025
yes still happening.
These are the commands i use to kill the python process on the pi:
sudo kill -kill $(ps aux|grep python | awk '{print $2}')
sudo kill -kill $(ps aux|grep python3 | awk '{print $2}')
After the python process is killed, then the debug won't work, unless we do "Developer: Reload Window" option (under View > Command Palette.) .
github-actions commentedon Jan 15, 2026
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
tmatw (@tojiamathewwork), you can help us out by closing this issue if the problem no longer exists, or adding more information.
tojiamathewwork commentedon Jan 15, 2026
I checked this today and the issue still exists.
eleanorjboyd commentedon Sep 23, 2026
🤖 Thanks for confirming this still happens. Could you reproduce it on the latest Python and Python Debugger extensions and provide: (1) the process list matched by
ps aux | grep pythonbefore it is killed, (2) whether both Run Python File in Terminal and Debug Python File fail afterward, and (3) the Python and Python Debugger output-channel logs from the failed attempt? The current kill command can match extension-owned processes based on their full command line, so those details will show whether this belongs here or in https://github.com/microsoft/vscode-python-debugger. Issues markedinfo-neededautomatically close after 30 days without a reply.tojiamathewwork1 commentedon Sep 23, 2026
VSCode remote debugging is broken.
Refer:
microsoft/vscode#326232