We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

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

  • 1 отговор
  • 1 има този проблем
  • 1 изглед
  • Последен отговор от 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.

Избрано решение

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

Прочетете този отговор в контекста 👍 0

Всички отговори (1)

more options

Избрано решение

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