Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Google Calendar won't load in Firefox

  • 7 antwoorden
  • 1 heeft dit probleem
  • 1 weergave
  • Laatste antwoord van jonzn4SUSE

more options

I'm using Firefox 84.0.2 on Ubuntu 18.04. It has suddenly stopped being able to load Google Calendar. It shows the banner for Google Calendar but no content, and the progress bar shows it continually trying to load. Even after several minutes there is no time-out. The problem persists in safe mode. No other Google products (Gmail, Google Drive) show this problem, and the calendar loads normally in Chrome. Any suggestions would be appreciated.

I'm using Firefox 84.0.2 on Ubuntu 18.04. It has suddenly stopped being able to load Google Calendar. It shows the banner for Google Calendar but no content, and the progress bar shows it continually trying to load. Even after several minutes there is no time-out. The problem persists in safe mode. No other Google products (Gmail, Google Drive) show this problem, and the calendar loads normally in Chrome. Any suggestions would be appreciated.

Gekozen oplossing

For reasons that I don't understand, Google Calendar is working again. It seems to have undergone a spontaneous remission. I did nothing to bring it about. Maybe the problem was with Google's servers.

Dit antwoord in context lezen 👍 0

Alle antwoorden (7)

more options

Yeah, I can replicate the issue. see screenshot

Operating System: openSUSE Tumbleweed 20210119 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600

more options

Works for me in safe mode. see screenshot

more options

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block content (Adblock Plus, NoScript, DuckDuckGo PE, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block content.

Firefox shows a purple shield instead of a gray shield at the left end of the location/address bar in case Enhanced Tracking Protection is blocking content. You can click shield icon for more detail and possibly disable the protection. You can check the Web Console for messages about blocked content.


You can try these steps in case of issues with webpages:

You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • hold down the Shift key and left-click the Reload button
  • press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • press "Command + Shift + R" (Mac)

Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).

"Remove the Cookies" for websites that cause problems:

  • Options/Preferences -> Privacy & Security
    Cookies and Site Data: "Manage Data"

"Clear the Cache":

  • Options/Preferences -> Privacy & Security
    Cookies and Site Data -> Clear Data -> Cached Web Content: Clear

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or userChrome.css is causing the problem.

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Safe Mode start window
more options

The site is hit or miss. I went back into safe mode and now it's not working. Let try another version.

more options

The works, but if I leave it and go back it stops working.

more options

Gekozen oplossing

For reasons that I don't understand, Google Calendar is working again. It seems to have undergone a spontaneous remission. I did nothing to bring it about. Maybe the problem was with Google's servers.

more options

Yes, the issue was a G Thing.