Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

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

Newer version of Thunderbird not recognizing older profile (experienced user)

  • 1 resposta
  • 1 tem este problema
  • 1 visualização
  • Última resposta por gbell12

more options

I installed Ubuntu 16.04 LTS on top of 12.04 LTS, which had an up-to-date Thunderbird running on it.

However, when I launch Thunderbird (45.3.0), it presents me with the "Welcome to Thunderbird" dialog and doesn't see any of my accounts (or folders).

I've confirmed that profiles.ini is pointing to the right folder. I've tried creating a new profile and copying the old profile's files and folders over to it. Same result.

No other symptoms. No error on stdout/stderr, no other messages. Just an apparently empty profile (which isn't empty at all on disk).

Do I need to resort to ImportExportTools?

Thanks much for the replies.

I installed Ubuntu 16.04 LTS on top of 12.04 LTS, which had an up-to-date Thunderbird running on it. However, when I launch Thunderbird (45.3.0), it presents me with the "Welcome to Thunderbird" dialog and doesn't see any of my accounts (or folders). I've confirmed that profiles.ini is pointing to the right folder. I've tried creating a new profile and copying the old profile's files and folders over to it. Same result. No other symptoms. No error on stdout/stderr, no other messages. Just an apparently empty profile (which isn't empty at all on disk). Do I need to resort to ImportExportTools? Thanks much for the replies.

Solução escolhida

SOLVED: prefs.js was corrupted... so it had no knowledge of the accounts, etc.

Ler esta resposta no contexto 👍 0

Todas as respostas (1)

more options

Solução escolhida

SOLVED: prefs.js was corrupted... so it had no knowledge of the accounts, etc.