No output from running cells after installation on Windows
See original GitHub issueDescription
I installed on Windows using the instructions in the README file. Everything appears fine, except running cells produces no output; e.g. if I open a new notebook, create a code cell with the code print(‘here’), and click the “run the selected cells and advance” button, the curser advances but no output is produced. Re-installing doesn’t fix this.
Reproduce
- Download .exe file from https://github.com/jupyterlab/jupyterlab-desktop/blob/master/README.md
- Install following setup prompts
- Open new notebook from the launcher
- Type any command that should produce output (e.g. a print statement)
- Click run cell
Expected behavior
Output should be produced but it isn’t. The curser moves to the next cell but no output is produced.
Context
- Operating System and version: Windows 10 pro
- JupyterLab-Desktop version: Version 3.2.5-2
- Installer: .exe
Troubleshoot Output
Paste the output from running `jupyter troubleshoot` from the terminal inside of JupyterLab-Desktop here. Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved.Try the new cross-platform PowerShell https://aka.ms/pscore6 PS C:\Users\Lea> jupyter troubleshoot
jupyter : The term ‘jupyter’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1
- jupyter troubleshoot
-
+ CategoryInfo : ObjectNotFound: (jupyter:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\Lea>
Hmm… the terminal doesn’t recognize this command.
You may want to sanitize the paths in the output.
Browser Output (required for interface issues after loading)
Paste the output from the DevTools JavaScript console here, if applicable.
Logs (required for issues with loading, server and startup)
Paste the logs from the mian.log file here.C:\Users<username>\AppData\Roaming\jupyterlab-desktop\logs exists as a path, but main.log is not there.
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (3 by maintainers)
Top GitHub Comments
Thanks! the main.log file is still not there though.
On Thu, Jan 6, 2022 at 10:32 AM Michał Krassowski @.***> wrote:
Hi, Actually, it looks like while that solution worked the first time, when I try to launch JupyterLab the same way again it doesn’t work. The first time (a few days ago) that I ran:
C:\JupyterLab\resources\jlab_server\condabin\activate
jlab .
It opened successfully. But now when I run the activate command, I get: [image: image.png]
If I try just running the jlab command without the activate command first, a dialog box pops up asking me to select the Python environment to use, but when I select “Use the bundled Python environment”, click “save and restart,” the dialog box simply pops up again in an endless cycle. I could try "Use custom Python environment, but I am not sure how to do that. [image: image.png]
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Virus-free. www.avg.com http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Thu, Jan 13, 2022 at 11:29 AM Zuckerman, Leah < @.***> wrote: