We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

startup script error, unable to show unknown toolbar

ysexton
ysexton
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.

Alle antwurden (1)

David McRitchie
David McRitchie
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.