vscode python extension not running in ubuntu 16.04 LTS.

[fieraloca]

Issue Type: Bug

Extension version: 2020.3.69010
VS Code version: Code 1.43.2 (0ba0ca52957102ca3527cf479571617f0de6ed50, 2020-03-24T07:52:11.516Z)
OS version: Linux x64 4.15.0-91-generic

VSCode Version:

Version: 1.43.2
Commit: 0ba0ca5
Date: 2020-03-24T07:52:11.516Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 4.15.0-88-generic

OS Version: Ubuntu 16.04 LTS

Steps to Reproduce:

1. Create and open a python file (testing.py; add a single line to it)

print('... testing'). 

2.Configure launch.json to use python.
3. Select Python: Interpreter.
I have tried with conda environments; and python 3.5; 3.6; 3.6 with same error result.
4. Run the debugger (F5).

Does this issue occur when all extensions are disabled?: Yes
Only python extension is enabled. Version : 2020.3.69010 (19 March 2020)

Error list

Error Window Popup

Session[1] timed out waiting for <debugpy.adapter.components.missing.<locals>.Missing object at 0x7fb9e2753cc0> to connect

Console output

(TESTSUITE) rpglover@u832f94cf022e52:~/Desktop/deleteme$  env DEBUGPY_LAUNCHER_PORT=40883 /anaconda3/envs/TESTSUITE/bin/python /rpglover/.vscode/extensions/ms-python.python-2020.3.69010/pythonFiles/lib/python/debugpy/no_wheels/debugpy/launcher /rpglover/Desktop/deleteme/testing.py 
Traceback (most recent call last):
  File "/anaconda3/envs/TESTSUITE/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/anaconda3/envs/TESTSUITE/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/rpglover/.vscode/extensions/ms-python.python-2020.3.69010/pythonFiles/lib/python/debugpy/no_wheels/debugpy/launcher/__main__.py", line 80, in <module>
    main()
  File "/rpglover/.vscode/extensions/ms-python.python-2020.3.69010/pythonFiles/lib/python/debugpy/no_wheels/debugpy/launcher/__main__.py", line 42, in main
    launcher.connect(launcher_port)
  File "/rpglover/.vscode/extensions/ms-python.python-2020.3.69010/pythonFiles/lib/python/debugpy/no_wheels/debugpy/launcher/../../debugpy/launcher/__init__.py", line 27, in connect
    sock.connect(("127.0.0.1", launcher_port))
ConnectionRefusedError: [Errno 111] Connection refused

[tysonpaul89]

I am also facing the same issue. I am also in Ubuntu 16.04 LTS.

I tried to downgrade the python extension to previous versions, but then the debugger will not start(no error shown on this case just. Terminal will show the initial debug command and it will not get executed).

I suspect this an OS related issue because on my laptop which is using Ubuntu 18.04 LTS doesn't have this issue.

This my launch.json.

{
   "version":"0.2.0",
   "configurations":[
      {
         "name":"Python: Current File",
         "type":"python",
         "request":"launch",
         "program":"${file}",
         "console":"integratedTerminal",
         "pythonPath":"/Projects/xxx/xxx/env/bin/python"
      },
      {
         "name":"Python: Django 8000",
         "type":"python",
         "request":"launch",
         "program":"${workspaceFolder}/manage.py",
         "console":"integratedTerminal",
         "pythonPath":"/Projects/xxx/xxx/env/bin/python",
         "args":[
            "runserver",
            "--noreload",
            "--nothreading"
         ],
         "django":true
      },
      {
         "name":"Python: Django 8001",
         "type":"python",
         "request":"launch",
         "program":"${workspaceFolder}/manage.py",
         "console":"integratedTerminal",
         "args":[
            "runserver",
            "8001",
            "--noreload",
            "--nothreading"
         ],
         "django":true
      },
      {
         "name":"Python Celery",
         "type":"python",
         "request":"launch",
         "program":"${workspaceFolder}/manage.py",
         "console":"integratedTerminal",
         "args":[
            "celeryd",
            "-Q",
            "cronJobQueueLow_LOCAL",
            "-l",
            "info",
            "-P",
            "solo"
         ],
         "django":true
      }
   ]
}

VSCode Version:

Version: 1.43.1
Commit: fe22a9645b44368865c0ba92e2fb881ff1afce94
Date: 2020-03-18T07:17:38.324Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 4.4.0-176-generic

Python Extension Version

Id: ms-python.python
Version: 2020.3.69010

[woodenshoe-isk]

I'm getting the same error on MacOS Catalina
OS: Catalina 10.15.4 (19E266)
VS Code: Version: 1.43.2 Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50
MS Python Extension: 2020.3.69010

[omartin2010]

I have the same error connecting from both Windows and MacOs, but using the remote extension to connect to a ubuntu 16.04 machine. And I just tested with the previous version of the python extension and for me, it works normally.

[int19h]

@fieraloca You've mentioned that you're hitting this issue with conda as well as system Python. For the latter, are you also creating virtual environments? Does it still happen if using the system interpreter directly?

[omartin2010]

In my case it happens without virtual envs. Straight os python3. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Pavel Minaev <notifications@github.com> Sent: Friday, March 27, 2020 7:08:16 PM To: microsoft/vscode-python <vscode-python@noreply.github.com> Cc: Olivier Martin <omartin@live.ca>; Comment <comment@noreply.github.com> Subject: Re: [microsoft/vscode-python] vscode python extension not running in ubuntu 16.04 LTS. (#10793) @fieraloca<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffieraloca&data=02%7C01%7C%7C4011a8f204534b52f2bb08d7d2a3bc22%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637209472981753115&sdata=1rjk5bJytTFH4BQ4fRoAKBXmZ7v8fCeDr5rHDoT242A%3D&reserved=0> You've mentioned that you're hitting this issue with conda as well as system Python. For the latter, are you also creating virtual environments? Does it still happen if using the system interpreter directly? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvscode-python%2Fissues%2F10793%23issuecomment-605350709&data=02%7C01%7C%7C4011a8f204534b52f2bb08d7d2a3bc22%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637209472981753115&sdata=geE%2BaXbbiNXCfp4%2BJTn06ap59YNiySJF5rcvcv%2B%2FOcc%3D&reserved=0>, or unsubscribe<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACWYKXUOXU4MP6P2I6CM4ZLRJUWWBANCNFSM4LTZL3DQ&data=02%7C01%7C%7C4011a8f204534b52f2bb08d7d2a3bc22%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637209472981763110&sdata=x7wieq34FNM01HEh4EPeW6i%2B3AfVzyA6hlFGWpFJdKs%3D&reserved=0>.

[fieraloca]

@int19h I have tried with both system python (with and without virtualenv) and with conda environments for python 3.5; 3.6 and 3.7. Same failure in all cases...