Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Firefox 63 Linux: tabs go blank and cannot be refreshed

  • 2 réponses
  • 1 a ce problème
  • 3 vues
  • Dernière réponse par Moilleadóir

more options

Since 63 arrived tabs that were loaded will randomly go blank, showing a loading animation. They cannot be refreshed and the only solution is to close the tab and recreate it. Since this seems to happen a lot with a Facebook *pinned* tab this makes pinning rather useless now.

Since 63 arrived tabs that were loaded will randomly go blank, showing a loading animation. They cannot be refreshed and the only solution is to close the tab and recreate it. Since this seems to happen a lot with a Facebook *pinned* tab this makes pinning rather useless now.

Toutes les réponses (2)

more options

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 is is causing the problem.

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

Try the Firefox version from the official Mozilla server if you currently use a version from the repositories of your Linux distribution.

more options

I am using Linux. Firefox hardware acceleration is automatically disabled - there is no support for it AT ALL. If you switch it on it does nothing.

I am using the default theme.

Using a manually downloaded version of Firefox sounds like a bad idea for ongoing security and stability. I’ll stick with the official repo thanks.

I will try Safe Mode eventually, but it makes using Firefox so difficult (e.g. not having access to a password manager) that it will be really painful running it long enough for this fault to appear.

I’m 99% sure this is related to the major changes that were released for Linux (Windows got them ages ago) with version 63.