Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

following the most recent update, upon startup firefox opens the print window; please make it stop.

  • 2 respostas
  • 1 tem este problema
  • 8 visualizações
  • Última resposta por willowmaybe

more options

Version 41.0.1 update installed earlier today. Upon automatic restart, Firefox subsequently showed two icons in the dock, and opens a print box upon startup every time now. I've restarted the computer several twice, and restarted Firefox numerous times, and it still continues. I'm running a Mac Air, OS X Yosemite, 10.10.5. Why? How can I get it to be normal again?

Version 41.0.1 update installed earlier today. Upon automatic restart, Firefox subsequently showed two icons in the dock, and opens a print box upon startup every time now. I've restarted the computer several twice, and restarted Firefox numerous times, and it still continues. I'm running a Mac Air, OS X Yosemite, 10.10.5. Why? How can I get it to be normal again?

Todas as respostas (2)

more options

Start with this;

Type about:preferences#general<enter> in the address bar.

There are two settings;

  • When Firefox Starts

When the browser is started, what do you want to display. Many of us choose Show My Home Page.

  • Home Page

When a new page is opened, what do you want displayed.

  1. Use Current Page. Use what ever page(s) are open at that time.
  2. Use Bookmark
  3. Restore To Default. about:home shows a Mozilla home page with tools.

You can use any of these that you wish;

about:home (Firefox default home page), about:newtab (shows the sites most visited), about:blank (a blank page),

or you can enter any web page or about: page you want.

more options

Thanks for the quick reply, though I think the problem is something more complicated than resetting my homepage. It seems to have resolved itself upon restarting and closing various tabs, so I think it was something to do with a page that was running. Thanks again for your swiftness.