Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

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

Private Browsing enabled, but it's unchecked in options and I don't want it

  • 4 respostas
  • 2 têm este problema
  • 3 visualizações
  • Última resposta por eatrightny

more options

I updated to FF 5 yesterday and when I rebooted I am in Private Browsing mode. I did not enable it. In Options, it NOT enabled. Stop PV is grayed out. I deleted the session.js file. I do NOT want to use PV - I want my saved tabs to come back up when I restart FF. Is there a real fix for this in FF5, or can I go back to 3.6 or 4.1? If so, how? thank you so much

I updated to FF 5 yesterday and when I rebooted I am in Private Browsing mode. I did not enable it. In Options, it NOT enabled. Stop PV is grayed out. I deleted the session.js file. I do NOT want to use PV - I want my saved tabs to come back up when I restart FF. Is there a real fix for this in FF5, or can I go back to 3.6 or 4.1? If so, how? thank you so much

Solução escolhida

Did yo check the command (target) line in the Firefox desktop shortcut to be sure that there isn't a -private switch appended?

See also:

Ler esta resposta no contexto 👍 0

Todas as respostas (4)

more options

Solução escolhida

Did yo check the command (target) line in the Firefox desktop shortcut to be sure that there isn't a -private switch appended?

See also:

more options

That was a great suggestion. There WAS a -private switch on the shortcut. Can't imagine how it got there, but I removed it and restarted FF and I got my tabs back. Thanks so much for your help. -d-

more options

Please click the Solved It button next to the answer that solved your Firefox support issue, it appears when you are logged in, so this thread gets marked as Solved to help other users who may have this same problem.

more options

thanks for letting me know the correct protocol, I'll be sure to remember that in the future.