Bookworm: Weird Firefox issue

[local10]

Hi,

Have been using Debian + Firefox with Tutanota email for a number of years and everything was fine until about a week ago when I started to get a blank empty white page when trying to access the Tutanota login page: https://mail.tutanota.com/login

Tried https://mail.tutanota.com/login in Chromium and it works as it should, that is, shows a proper log in page with the ID and password fields, no issues. Tried https://mail.tutanota.com/login in Firefox v126 but still got an empty white page.

Any ideas? Thanks

$ aptitude show firefox-esr
Package: firefox-esr                     
Version: 115.11.0esr-1~deb12u1

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8
Kernel Version: 6.1.0-21-amd64 (64-bit)
Graphics Platform: X11

[Charles Curley]

On Wed, 22 May 2024 23:02:17 +0200 (CEST)

Post by local10
Have been using Debian + Firefox with Tutanota email for a number of
years and everything was fine until about a week ago when I started
to get a blank empty white page when trying to access the Tutanota
login page: https://mail.tutanota.com/login
Tried https://mail.tutanota.com/login in Chromium and it works as it
should, that is, shows a proper log in page with the ID and password
fields, no issues. Tried https://mail.tutanota.com/login in Firefox
v126 but still got an empty white page.
Any ideas? Thanks
$ aptitude show firefox-esr
Package: firefox-esr                     
Version: 115.11.0esr-1~deb12u1

I get what looks like a proper log-in page on both firefox and vivaldi
(a derivative of chromium).

BTW, they are advising of a change in log-in URL.

***@hawk:~$ pre firefox vivaldi
firefox-esr 115.11.0esr-1~deb12u1 amd64
vivaldi-stable 6.7.3329.31-1 amd64
***@hawk:~$

Try a hard refresh to clear your cache: ctl-r.

[Michael Kjörling]

Post by Charles Curley

Post by local10
about a week ago when I started
to get a blank empty white page when trying to access the Tutanota
login page: https://mail.tutanota.com/login

I get what looks like a proper log-in page on both firefox and vivaldi

Works fine for me too, on the same firefox-esr package version.

If clearing the browser cache doesn't help, try with a brand new fresh
profile. `firefox --no-remote --new-instance --ProfileManager` should
be a good start. If it works in a brand new profile, it's _something_
about your Firefox settings.

[local10]

Post by Michael Kjörling
Works fine for me too, on the same firefox-esr package version.
If clearing the browser cache doesn't help, try with a brand new fresh
profile. `firefox --no-remote --new-instance --ProfileManager` should
be a good start. If it works in a brand new profile, it's _something_
about your Firefox settings.

I've tried the following but it didn't help:

   1. FF 115.11.0esr (64-bit) with a new profile
   2. FF v126 with a new profile
   3. Purged (aptitude purge) and reinstalled FF 115.11.0esr again

Looked into this further (using Web Developer Tools, Ctrl+Shift+I, Network tab)) and it appears that when the log in page is loading  the "gui-base-TfJ0d3Pr.js <https://mail.tutanota.com/gui-base-TfJ0d3Pr.js>"  script fails to fully load with the "NS_ERROR_NET_PARTIAL_TRANSFER" error.

Am really puzzled as to why this script fails to load now. Tutanota had worked fine for me for years until this issue showed up a week ago.

The FF console shows the following:

Loading failed for the <script> with source “https://mail.tutanota.com/gui-base-TfJ0d3Pr.js”. login:1:1
error Error: https://mail.tutanota.com/gui-base-TfJ0d3Pr.js, https://mail.tutanota.com/sanitizer-qpXkKHr8.js (SystemJS https://git.io/JvFET#3)
    instantiate https://mail.tutanota.com/polyfill.js:1
x.instantiate/</<@https://mail.tutanota.com/polyfill.js:1:6483
Logger.ts:89:18
Encountered error when trying to handle errors with ErrorHandlerImpl Error: https://mail.tutanota.com/gui-base-TfJ0d3Pr.js, https://mail.tutanota.com/sanitizer-qpXkKHr8.js (SystemJS https://git.io/JvFET#3)
    instantiate https://mail.tutanota.com/polyfill.js:1
Logger.ts:99:18
error Error: https://mail.tutanota.com/gui-base-TfJ0d3Pr.js, https://mail.tutanota.com/sanitizer-qpXkKHr8.js (SystemJS https://git.io/JvFET#3)
    instantiate https://mail.tutanota.com/polyfill.js:1
x.instantiate/</<@https://mail.tutanota.com/polyfill.js:1:6483
Logger.ts:89:18
error Error: https://mail.tutanota.com/gui-base-TfJ0d3Pr.js, https://mail.tutanota.com/sanitizer-qpXkKHr8.js (SystemJS https://git.io/JvFET#3)
    instantiate https://mail.tutanota.com/polyfill.js:1
x.instantiate/</<@https://mail.tutanota.com/polyfill.js:1:6483
Logger.ts:89:18
....


Thanks to everyone who responded.

[Henning Follmann]

Post by local10

Post by Michael Kjörling
Works fine for me too, on the same firefox-esr package version.
If clearing the browser cache doesn't help, try with a brand new fresh
profile. `firefox --no-remote --new-instance --ProfileManager` should
be a good start. If it works in a brand new profile, it's _something_
about your Firefox settings.

   1. FF 115.11.0esr (64-bit) with a new profile
   2. FF v126 with a new profile
   3. Purged (aptitude purge) and reinstalled FF 115.11.0esr again

[...]

I had a similar issue 6 month ago.
I also tried those steps without any success.

Then I created a new account and there the issue did not appear.
So, I thought, it has to be something account specific.

I deleted these directories:
~/.cache/mozilla/firefox
~/.mozilla/firefox

At the next launch firefox greated me with the new user welcome.
You have to start from scratch but it resolved the issue.

-H

[Roland Müller]

Hello,

sometimes some cooperative sites had similar problems e.g MS's O365 or
Oracle's support site. In these cases removing stored cookies and
website data helped.

In addition cache can be deactivated in FF Developer Console
(Ctrl-Shift-k) in the tab "Network(ing)". Here you have a checkbox for
deactivating the cache in the top row of the tab.

Then check FF's privacy protection for blocked trackers.

BR,

Roland

Post by Henning Follmann

Post by local10

Post by Michael Kjörling
Works fine for me too, on the same firefox-esr package version.
If clearing the browser cache doesn't help, try with a brand new fresh
profile. `firefox --no-remote --new-instance --ProfileManager` should
be a good start. If it works in a brand new profile, it's _something_
about your Firefox settings.

   1. FF 115.11.0esr (64-bit) with a new profile
   2. FF v126 with a new profile
   3. Purged (aptitude purge) and reinstalled FF 115.11.0esr again

[...]
I had a similar issue 6 month ago.
I also tried those steps without any success.
Then I created a new account and there the issue did not appear.
So, I thought, it has to be something account specific.
~/.cache/mozilla/firefox
~/.mozilla/firefox
At the next launch firefox greated me with the new user welcome.
You have to start from scratch but it resolved the issue.
-H