Jupyter notebooks not working

[gabriel19913]

Describe the bug
Even if I chose an environment with Jupyter installed Vscodium asks me to install again. After this the kernel's notebook doesn't connect. The same environment is working just fine in VsCode.

Please confirm that this problem is VSCodium-specific

• 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

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

To Reproduce
Steps to reproduce the behavior:

1. Go to a .ipynb file
2. Select an environment with jupyter installed
3. Click to connect in the kernel
4. Nothing happens.

Expected behavior
I expected to connect in the kernel so I can execute the code using jupyter

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: PopOS 20.04
• Architecture x64
• Version 1.48.2

Additional context
Add any other context about the problem here.

[haykkh]

Just experienced the same issues (it autostarting the server in VSCode but no Codium).

Have you tried:

1. Command+Shift+P
2. >Python: Select Intepreter to start jupyter notebook server
3. Reopening the notebook

(not just selecting the environment on the bottom left)

[wbm37]

I am also experiencing the same issue. It works in VScode, but not in VSCodium. I figured maybe it was a firewall issue, but I turned it off and tested and it didn't work. I have tried what haykkh said, but it did not resolve the issue.

[rafaelsf80]

Same issue here, Jupyter extension stopped working since some days. May be related to the latest update to 1.51.1 #558.

I rolled back to 1.50.1 and it works

[stripedpajamas]

#558 says it's fixed in latest version (1.52.1). Can you confirm?

[robert-elles]

I have the same issue in vscodium 1.59.0-1. I tried selecting the python interpreter of my pipenv setup with

Python: Select Intepreter to start jupyter notebook server

but after reopening the notebook it still asks me to select a kernel or install one from the marketplace. I have no idea how to work around this issue.

[matbarc]

I have been having the same issue as @robert-elles ever since I updated to 1.59.0-1. Now every time I open a Jupyter notebook file directly by left-clicking it, VSCodium opens a different editor than the one it usually did and it prompts me to install a Kernel from the marketplace in order to run. Right-clicking the file, though, and selecting 'Open in Notebook Editor' opens the usual editor and works normally.

[zelad]

again this problem with the last version (1.66). I uninstalled it, took a portable version ( 1.65 ). Windows ( 10 ) asked me the rights for the firewall and it's gone again...