You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting two prompts of Jupyter_bin asking for keychain access. I don't see why I need it, so I've been hitting deny.
The first prompt is blocking the Chromium app from starting up. Once I deny it, it starts up with no problem.
When I deny the second prompt, it seems like it's triggering the auto-terminal-shutdown. If I ignore it, JupyterLab works fine. If I deny it, my terminal session closes, and my JupterLab window that is still open loses connection to all of the kernels.
macOS High Sierra 10.13.6
Installed from commit 0021964faae8423282ecd4828e16b618c12b90b8
The text was updated successfully, but these errors were encountered:
For any given instance of Chrome or Chromium on OSX, you need to give it access to "Chromium Safe Storage" in your keychain. This value is generated the first time Chrom/-ium is run on your system, and is used to encrypt sensitive user settings, such as logins and password.
Bottom line, Chrom/-ium needs this value to run, so you need to allow access. There is no security risk here
telamonian
changed the title
Jupyter_bin asks for keychain access, denying seems to trigger session termination
Access to "Chromium Safe Storage" is requested on first startup of jupyter-app
Apr 2, 2021
I'm getting two prompts of
Jupyter_bin
asking for keychain access. I don't see why I need it, so I've been hitting deny.The first prompt is blocking the Chromium app from starting up. Once I deny it, it starts up with no problem.
When I deny the second prompt, it seems like it's triggering the auto-terminal-shutdown. If I ignore it, JupyterLab works fine. If I deny it, my terminal session closes, and my JupterLab window that is still open loses connection to all of the kernels.
macOS High Sierra 10.13.6
Installed from commit
0021964faae8423282ecd4828e16b618c12b90b8
The text was updated successfully, but these errors were encountered: