vscodium
vscodium copied to clipboard
Blanck screen when trying open Jupyter Notebook
Describe the bug Jupyter notebook extension is no more working. I obtain blanck screen when i try open new Jupyter notebook or existing one. I have no error message 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. => I did find a close bug report but it says that version 1.52.1 fixed it. I have that current version but the bug is real.
To Reproduce Steps to reproduce the behavior: 1 )Do 'ctrl + shift +p' choose 'Python : Create a New Blanck Jupyter Notebook' => new 'untitled-x.ipynb' opened but stay blanck and impossible to write in. 2) Opening an existing jupyter noteboock => blanck screen after connecting the kernel
Screenshots
If applicable, add screenshots to help explain your problem.
on VSCodium:
On VSCode:
Desktop (please complete the following information):
- OS: Windows 10 19041.685
- Architecture [x64]
- Version [e.g. 1.52.1]
Additional context Add any other context about the problem here.
For me uninstalling and reinstalling the Python extension did solve this. Problem didn't reoccur since.
@echidne have you tried uninstalling/reinstalling the Python extension as mentioned by @jalemann ?
@stripedpajamas I just tried it now and its working. Look like the update of VS codium corrupted somewaht the Python extension. previously i fixed it in downgrading VS Codium to 1.50.1. But for me the issue is still existing since you have to uninstall and reinstall Python to have your jupyter extension working. Something is not working correctly in the udpdate of Vs Codium
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.