Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

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

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by gbell12

gbell12
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.

Chosen solution

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

Read this answer in context 👍 0

All Replies (1)

gbell12
gbell12 Question owner
more options

Chosen Solution

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