Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

startup script error, unable to show unknown toolbar

  • 1 risposta
  • 4 hanno questo problema
  • 4 visualizzazioni
  • Ultima risposta di David McRitchie

more options

When I start Firefox, I get an error box that says: Warning: unresponsive script, chrome://tavgp/content/libs/include.js:595 Continue or Cancel After clicking on one, Firefox starts and there is a message under the address bar that says: Firefix is not able to show the Toolbar, Please re-install the Toolbar. I have no idea what toolbar it is about. Everything is displayed that I know about. I am an advanced user.

When I start Firefox, I get an error box that says: Warning: unresponsive script, chrome://tavgp/content/libs/include.js:595 Continue or Cancel After clicking on one, Firefox starts and there is a message under the address bar that says: Firefix is not able to show the Toolbar, Please re-install the Toolbar. I have no idea what toolbar it is about. Everything is displayed that I know about. I am an advanced user.

Tutte le risposte (1)

more options

The problem is AVG Safe search and AVG Security Toolbar

For more information see:
https://support.mozilla.com/en-US/questions/843822

Don't think anyone has mentioned the message under the toolbar before. You may be getting that as the extension should be blocked by the Firefox blocklist. see Nov 29 2010. Anyway it has been a problem in Firefox 2 and latter.