Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

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

  • 1 wotmołwa
  • 1 ma tutón problem
  • 3 napohlady
  • Poslednja wotmołwa wot 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.

Wubrane rozrisanje

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

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (1)

more options

Wubrane rozrisanje

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