Recently, I installed JupyterLab desktop - Version 3.2.4.1 I have multiple problems working with this environment. Just for the beginning:
When running New Launcher, not showing an option for Terminal. Even I have set
in file page_config.json in my user directory “terminalsAvailable”: true.
I can run JupyterLab PowerShell separately.
When I try run conda info from lab notebook, I got the message: Note: you may need to restart the kernel to use updated packages. and the restarting kernel doesn’t change this message. Running conda info from shell get me:
(base) PS C:\Users\User> conda info
active environment : base
active env location : C:\JupyterLab\resources\jlab_server
shell level : 1
user config file : C:\Users\User\.condarc
populated config files : C:\JupyterLab\resources\jlab_server.condarc
C:\Users\User.condarc
conda version : 4.11.0
conda-build version : not installed
python version : 3.8.12.final.0
virtual packages : __win=0=0
__archspec=1=x86_64
base environment : C:\JupyterLab\resources\jlab_server (writable)
conda av data dir : C:\JupyterLab\resources\jlab_server\etc\conda
conda av metadata url : None
channel URLs : conda-forge/win-64 conda-forge/noarch
package cache : C:\JupyterLab\resources\jlab_server\pkgs
C:\Users\User.conda\pkgs
C:\Users\User\AppData\Local\conda\conda\pkgs
envs directories : C:\Users\User.conda\envs
C:\JupyterLab\resources\jlab_server\envs
C:\Users\User\AppData\Local\conda\conda\envs
platform : win-64
user-agent : conda/4.11.0 requests/2.26.0 CPython/3.8.12 Windows/10 Windows/10.0.14393
administrator : False
netrc file : None
offline mode : False
I can install new packages, create new conda env in shell, but can’t see it in JupyterLab desktop. Any help?
JupyterLab Desktop 3.2.4-1 is old at this point (we had 3 releases since; please upgrade to 3.2.5-1 or newer if you are reading it in after the weekend where I suspect a release might happen).
I can install new packages, create new conda env in shell, but can’t see it in JupyterLab desktop. Any help?
what is “it”? Is there a specific package that you have installed but don’t see it in JupyterLab Desktop? Or is it a new environment that you created and don’t see it? Did you select and environment using the environment picker in the statusbar?
I uninstalled JupyterLab Desktop 3.2.4-1 by instructions, get installation error:
After complete uninstall, install a new version 3.2.5-2.
Now JupyterLab can’t connect to kernel.
Is this the problem in the default environment, or in your environment?
What are the final ~50 logs in %USERPROFILE%\AppData\Roaming\jupyterlab-desktop\logs\main.log?
Are there any logs in the developer console? Go to Help menu → Open Developer Console to access the JavaScript console, paste the output from the DevTools JavaScript console here.
answers to my previous questions - help me help you.
I have only ipykernel immediately after the new installation, I have only one default environment.
This is the contents of main.log:
[2021-12-20 20:24:22.506] [info] In production mode
[2021-12-20 20:24:22.511] [info] Logging to file (C:\Users\User\AppData\Roaming\jupyterlab-desktop\logs\main.log) at ‘false’ level
[2021-12-20 20:24:22.573] [error] (node:380) DeprecationWarning: findLogPath() is deprecated and will be removed in v5.
(Use JupyterLab --trace-deprecation ... to show where the warning was created)
[2021-12-20 20:24:30.116] [error] (node:380) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15. See Make nativeWindowOpen: true the default · Issue #28511 · electron/electron · GitHub for more information.
[2021-12-20 20:24:32.237] [info] Jupyter Server initialization message: C:\JupyterLab\resources\jlab_server\lib\site-packages\traitlets\traitlets.py:2202: FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use ‘’ instead of ‘""’ if you require traitlets >=5.
warn(
C:\JupyterLab\resources\jlab_server\lib\site-packages\traitlets\traitlets.py:2202: FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use ‘’ instead of '""’ if you require traitlets >=5.
warn(
[I 2021-12-20 20:24:32.236 ServerApp] jupyterlab | extension was successfully linked.
[2021-12-20 20:24:32.257] [info] Jupyter Server initialization message: [I 2021-12-20 20:24:32.257 ServerApp] Writing Jupyter server cookie secret to C:\Users\User\AppData\Roaming\jupyter\runtime\jupyter_cookie_secret
[2021-12-20 20:24:32.874] [info] Jupyter Server initialization message: [I 2021-12-20 20:24:32.874 ServerApp] nbclassic | extension was successfully linked.
[2021-12-20 20:24:33.034] [info] Jupyter Server initialization message: [W 2021-12-20 20:24:33.033 ServerApp] Terminals not available (error was DLL load failed while importing winpty: The specified procedure could not be found.)
[2021-12-20 20:24:33.047] [info] Jupyter Server initialization message: [I 2021-12-20 20:24:33.047 ServerApp] nbclassic | extension was successfully loaded.
[2021-12-20 20:24:33.048] [info] Jupyter Server initialization message: [I 2021-12-20 20:24:33.048 LabApp] JupyterLab extension loaded from C:\JupyterLab\resources\jlab_server\lib\site-packages\jupyterlab
[2021-12-20 20:24:33.049] [info] Jupyter Server initialization message: [I 2021-12-20 20:24:33.048 LabApp] JupyterLab application directory is C:\JupyterLab\resources\jlab_server\share\jupyter\lab
[2021-12-20 20:24:33.053] [info] Jupyter Server initialization message: [I 2021-12-20 20:24:33.053 ServerApp] jupyterlab | extension was successfully loaded.
[2021-12-20 20:24:33.054] [info] Jupyter Server initialization message: [I 2021-12-20 20:24:33.054 ServerApp] Serving notebooks from local directory: C:\Users\User
[I 2021-12-20 20:24:33.054 ServerApp] Jupyter Server 1.13.1 is running at:
react-dom.development.js:26244 Download the React DevTools for a better development experience: https://reactjs.org/link/react-devtoolsYou might need to use a local HTTP server (instead of file://): react/packages/react-devtools at main · facebook/react · GitHub
20:24:34.633 › $ref: keywords ignored in schema at path “#/properties/codeCellConfig”
20:24:34.638 › $ref: keywords ignored in schema at path “#/properties/markdownCellConfig”
20:24:34.639 › $ref: keywords ignored in schema at path “#/properties/rawCellConfig”
20:24:34.642 › $ref: keywords ignored in schema at path “#/properties/codeCellConfig”
20:24:34.643 › $ref: keywords ignored in schema at path “#/properties/markdownCellConfig”
20:24:34.645 › $ref: keywords ignored in schema at path “#/properties/rawCellConfig”
20:24:35.786 › Disabling terminals plugin because they are not available on the server
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/5d14207a-910f-47d6-afd0-6bce26eb5113/channels?session_id=9ba2f5ce-f8be-4985-9c38-6316fecccb32’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/5d14207a-910f-47d6-afd0-6bce26eb5113/channels?session_id=aaddf7ab-8d4c-4d42-bc2a-05ed0d19d3fb’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/5d14207a-910f-47d6-afd0-6bce26eb5113/channels?session_id=0494202b-2040-47ec-b068-3edbafd3173b’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
future.js:179 Uncaught (in promise) Error: Canceled future for comm_info_request message before replies were done
at KernelShellFutureHandler.dispose (future.js:179)
at default.js:999
at Map.forEach ()
at KernelConnection._clearKernelState (default.js:998)
at KernelConnection.dispose (default.js:319)
at KernelConnection._updateStatus (default.js:973)
at KernelConnection.handleShutdown (default.js:559)
at manager.js:233
at Set.forEach ()
at KernelManager.requestRunning (manager.js:231)
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/84c09c3f-6dd9-4fc9-8752-107a0866c8c4/channels?session_id=88bd1b4e-d3d1-4a16-8c51-25ea41ea1dde’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/84c09c3f-6dd9-4fc9-8752-107a0866c8c4/channels?session_id=e02f82d1-a900-46b2-8a7d-c713d76b504c’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/84c09c3f-6dd9-4fc9-8752-107a0866c8c4/channels?session_id=cd87c383-a618-41c5-8d1f-52f008e63ba0’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/42e088b9-5f10-4919-96e5-0174ddc46070/channels?session_id=389a540a-9068-4152-ac6d-18ba4f9eb02f’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/42e088b9-5f10-4919-96e5-0174ddc46070/channels?session_id=b244c012-6870-4251-94e4-4288c551ca87’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
default.js:958 WebSocket connection to ‘ws://localhost:8888/api/kernels/42e088b9-5f10-4919-96e5-0174ddc46070/channels?session_id=a7386471-8a8f-410a-926c-954f5ac555ce’ failed: WebSocket is closed before the connection is established.
_clearSocket @ default.js:958
Thank you. Unfortunately I don’t see anything helpful in the logs. I would recommend trying to uninstall clean once again, removing any trace that might be left of JupyterLab-Desktop and JupyterLab-App and only then installing again. Apologies for the inconvenience and the trouble.
