搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

extensions toolbar cannot be deactivated

  • 9 回覆
  • 1 有這個問題
  • 12 次檢視
  • 最近回覆由 guigs

more options

Good morning,

In Iceweasel 38.01 I cannot permanently deactivate the extensions toolbar. There is not a single button on it and the option from the context-menu operates normally. But the toolbar reappears each time upon starting up the browser. I cannot locate a second configuration- or customization option, nor the pertinent help-text, if there is one, which allowed me to permanently get rid of the useless toolbar.

Thank you for any hints.

Good morning, In Iceweasel 38.01 I cannot permanently deactivate the extensions toolbar. There is not a single button on it and the option from the context-menu operates normally. But the toolbar reappears each time upon starting up the browser. I cannot locate a second configuration- or customization option, nor the pertinent help-text, if there is one, which allowed me to permanently get rid of the useless toolbar. Thank you for any hints.

所有回覆 (9)

more options

It is possible to Refresh Firefox - reset add-ons and settings, however you may find more help in the iceweasal/ Debian forums.

more options

Is this toolbar present here?

  • "3-bar" Firefox menu button > Customize > Show/Hide Toolbars
  • View > Toolbars
    Tap the Alt key or press F10 to show the Menu Bar
  • Right-click empty toolbar area

Can you attach a screenshot?

  • Use a compressed image type like PNG or JPG to save the screenshot
  • Make sure that you do not exceed the maximum size of 1 MB
more options

guigs2 said

It is possible to Refresh Firefox - reset add-ons and settings, however you may find more help in the iceweasal/ Debian forums.

This worked for the moment after the refresh. As after restart the browser-window is configured not any differently than before, I have to ask, if a profile-setting should be taken into consideration for the reset-procedure..?

more options

cor-el said

Is this toolbar present here?
  • "3-bar" Firefox menu button > Customize > Show/Hide Toolbars

No.

  • View > Toolbars

Yes. This menu identical to the lower part of the context-menu.

  • Right-click empty toolbar area

Yes. See my original message, above.

Can you attach a screenshot?

Click the URLs for bigger images : http://pix.toile-libre.org/?img=1434437834.png
http://pix.toile-libre.org/?img=1434437991.png

more options

Missed a third screen shot. Here it is.

more options

You can't hide that toolbar via the View > Toolbars menu?

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window
more options

cor-el said

You can't hide that toolbar via the View > Toolbars menu?

Yes I can and always could. But upon restarting the browser, the empty extension bar is always there.

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

In Safe Mode, the extension bar is not displayed and does also not appear neither in the view-, nor in the context-menu.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance

Did that. The extension toolbar is still showing, each time, that I start the browser, irrespective of the state that I left it in (extension bar disabled or not) or the fact that I quit the browser in safe mode.

  • Do NOT click the Reset button on the Safe Mode start window

Iceweasel may be different from the ordinary Firefox release in that it does not even show a Reset button on that dialog.

Sorry. The extension bar is still taking up space while being completely useless. But I can live with that for the time.

more options

Also, I forgot to add, that by disabling extensions one by one and restarting with the extensions toolbar disabled, it is showing again anyway. I cannot identify a single extension which would be responsible for this misbehavior.

more options

It also looks like this was a past work around, however I am not an expert in the iceweasel builds: