Clean pip install of v7.0.2 launches blank web page at localhost/tree in FireFox, but works in Google Chrome #7009
Comments
|
Yesterday, I installed a fresh install of Notebook 7.0.2, and Firefox 102.13.0esr displayed the UI as expected. Not sure whether the problem is related to the mainline Firefox releases. |
Latest esr is 115.1.0esr, but I suspect the issue is something recent in FF mainline. My institution requires regular mainline updates. Things were working a couple of weeks ago. Considering the rapidity of mainline updates that could have been a couple of updates ago. |
|
I have seen similar things with Safari on macOS. I think it may be related to caches and token/password security. Switching between localhost and 127.0.0.1 seems to help, as does trying a different port from 8888. |
That appears to be it. Switching from localhost, which is the default to 127.0.0.1 fixes the problem. Now the question is if the cache issue is MacOS related or FireFox related? As Chrome and older FireFoxes work I am inclined to believe it is FF. |
|
I have the similiar problem with fresh new install 7.0.2 with Google Chrome 115.0.5790.170 |
Is this also on MacOS? |
|
Hmm, I am having a similar issue except its Safari failing, not Firefox. Login pages is fine, post login seemingly blank page on Safari (with some JS in page source, but not much else). In Safari's console, I do see: There is a brief stutter / pause, but the notebook fully loads as expected in both Firefox and Chrome (and no console errors) On a mac. (Apple Silicon, Ventura 13.5 (22G74)) |
|
I don't think this has anything to do with the particular browser: it is something like a cache problem in whatever browser you normally use, or were using before the upgrade. Does seem to be related to macOS, somehow, but maybe that is reporting bias? |
|
Oh snap, you are right. I feel like an idiot. Hard refreshed and I am working in Safari now. (Same ~0.5s stutter load as the other browsers, but otherwise fine, no more console errors). |
Yes! macOS: Monterey |
|
I have verified that this is a cookie and caching issue. I discovered that my institution's defaults for FF cause it to save everything across launches of the browser. At some point this overrode my preference to clear the cache on each restart. Manually clearing the cache and cookies caused things to work properly. I have reset my browser to my preference of clearing everything on relaunch. I am still mystified as to why lab still worked while notebook did not. Thus, I am leaving this open for 24 more hours in case somebody thinks that discrepancy should be pursued. After that I will close the issue as resolved by forcing clearing of caches. |
|
I had this problem with Firefox on WSL (windows subsystem for linux). It happened after I created a new virtual environment with a fresh notebook install. I erased all of my history for firefox and it appears to be working again. |
|
Same problem here, switching between localhost and 127.0.0.1 does not help. If this happens on different browsers, why has this issue been closed? Not dealing with caching properly seems to be a bug in the notbook program to me. |
Description
A clean install of notebook into a new virtual environment launches without populating any information in the Home page in FireFox 116.0.2, but works in recent Google Chrome.
Jupyter labcommand works in both.This may be a FireFox issue, but I am not sure what to report. Help with diagnosis would be appreciated.
The page source does contain some javascript:
Reproduce
pipenv shell).pip install notebook(does not seem to matter if manually install lab first).jupyter notebook.A blank page opens in my browser (latest Firefox).
Expected behavior
I expect the standard list of files and notebooks in the working directory.
Context
Troubleshoot Output
Command Line Output
Browser Output
Uncaught (in promise) TypeError: g[e] is undefined v http://localhost:8888/static/notebook/bundle.js:1 53680 http://localhost:8888/static/notebook/3680.bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 I http://localhost:8888/static/notebook/bundle.js:1 e http://localhost:8888/static/notebook/bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 89605 http://localhost:8888/static/notebook/9605.bundle.js:2 v http://localhost:8888/static/notebook/bundle.js:1 I http://localhost:8888/static/notebook/bundle.js:1 e http://localhost:8888/static/notebook/bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 32549 http://localhost:8888/static/notebook/2401.bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 72401 http://localhost:8888/static/notebook/2401.bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 I http://localhost:8888/static/notebook/bundle.js:1 e http://localhost:8888/static/notebook/bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 65733 http://localhost:8888/static/notebook/5733.bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 I http://localhost:8888/static/notebook/bundle.js:1 e http://localhost:8888/static/notebook/bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 60880 http://localhost:8888/static/notebook/880.bundle.js:1 60880 http://localhost:8888/static/notebook/880.bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 promise callback*37559 http://localhost:8888/static/notebook/bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 http://localhost:8888/static/notebook/bundle.js:1 http://localhost:8888/static/notebook/bundle.js:1 [bundle.js:1:511](http://localhost:8888/static/notebook/bundle.js) 60880 http://localhost:8888/static/notebook/880.bundle.js:1 (Async: EventListener.handleEvent) 60880 http://localhost:8888/static/notebook/880.bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 (Async: promise callback) 37559 http://localhost:8888/static/notebook/bundle.js:1 v http://localhost:8888/static/notebook/bundle.js:1 http://localhost:8888/static/notebook/bundle.js:1 http://localhost:8888/static/notebook/bundle.js:1The text was updated successfully, but these errors were encountered: