Vscodium: python extension - interpreter selector not showing on status bar

[juliuswz]

Describe the bug
Interpreter selector don't show when open a python file.

Please confirm that this problem is VSCodium-specific

• [x] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

• [x] I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

1. Open a Python file and wait for the extension to activate. Notice the interpreter not showing on the status bar.

Screenshots

Expected behavior

Actual behaviour

The extension is activated (it even activates my virtual environment when I create a new terminal) and working normally, I just can't see the interpreter on the status bar.

Desktop (please complete the following information):

• OS: [ Arch Linux ]
• Architecture [ x64 ]
• Version [ 1.50.0 ]

Additional context

Logs:
Output for Python in the Output panel:

User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'ShowExtensionSurveyPrompt - control'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'LocalZMQKernel - experiment'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'EnableIPyWidgets - experiment'
User belongs to experiment group 'RunByLine - control'
User belongs to experiment group 'CustomEditorSupport - control'
User belongs to experiment group 'pythonaacf'
> conda --version
> pyenv root
> python3.7 ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3.6 ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3 ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python2 ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> ~/venv/python3.8/bin/python ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> conda info --json
Error 2020-10-13 23:38:25: Failed to check if file needs to be fixed [EntryNotFound (FileSystemError): '/home/julius/.config/Code/User/settings.json' (EntryNotFound (FileSystemError): Error: ENOENT: no such file or directory, open '/home/julius/.config/Code/User/settings.json')
    at _handleError (/usr/share/vscodium-bin/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:725:473)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at async y.readText (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:1:498547)
    at async p.doesFileNeedToBeFixed (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:961593)
    at async /home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:960720
    at async Promise.all (index 0)
    at async p.getFilesToBeFixed (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:960666)
    at async p.updateTestSettings (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:960293)] {
  code: 'FileNotFound',
  name: 'EntryNotFound (FileSystemError)'
}
> ~/venv/python3.8/bin/python ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import notebook"
> ~/venv/python3.8/bin/python ~/.vscode-oss/extensions/ms-python.python-2020.9.112786/pythonFiles/pyvsc-run-isolated.py -c "import jupyter"
Starting Jedi Python language engine.
Python interpreter path: /home/julius/venv/python3.8/bin/python
Error 2020-10-13 23:38:26: Python Extension: interpreterManager.refresh [Error: [ms-python.python]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api ms-python.python
    at a (/usr/share/vscodium-bin/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:655:99)
    at Object.t.checkProposedApiEnabled (/usr/share/vscodium-bin/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:655:567)
    at Object.get activeNotebookEditor [as activeNotebookEditor] (/usr/share/vscodium-bin/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:1003:116)
    at u.get activeNotebookEditor [as activeNotebookEditor] (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:54:383170)
    at u.get hidden [as hidden] (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:642106)
    at /home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:844423
    at Array.every (<anonymous>)
    at g.updateVisibility (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:844411)
    at g.updateDisplay (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:844284)
    at async g.refresh (/home/julius/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:843237)]

[vvatelot]

Exact same error here

Version : 1.50.1
Commit : d2e414d9e4239a252d1ab117bd7067f125afd80a
Date : 2020-10-15T11:13:06.921Z
Electron : 9.2.1
Chrome : 83.0.4103.122
Node.js : 12.14.1
V8 : 8.3.110.13-electron.0
OS : Linux x64 5.4.0-52-generic

[Razique]

I confirm the issue on MacOS

Version: 1.50.1
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-15T11:18:43.323Z (4 days ago)
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.6.0

[Baldomo]

Same here, using the command line option makes it work as intended though

Version: 1.50.1
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-15T11:13:06.921Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.9.1-arch1-2-g14

[elmaghallawy]

same error here

Version: 1.51.0
Commit: fcac248b077b55bae4ba5bab613fd6e9156c2f0c
Date: 2020-11-06T10:57:27.345Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.8.18-300.fc33.x86_64

[alexdesiqueira]

Same issue. Running Debian Testing:

Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-12T00:31:42.540Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.9.0-2-amd64

[cleversonahum]

Same issue here using:

Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-12T10:54:25.653Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.4.80-2-MANJARO

[elmaghallawy]

Hi there, the issue is fixed for me now on

Version: 1.52.0
Commit: 940b5f4bb5fa47866a54529ed759d95d09ee80be
Date: 2020-12-12T00:37:51.866Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.9.13-200.fc33.x86_64

[alexdesiqueira]

Working for me on 1.52 as well:

Version: 1.52.0
Commit: 940b5f4bb5fa47866a54529ed759d95d09ee80be
Date: 2020-12-12T00:37:51.866Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.9.0-4-amd64

Thank you everyone!