Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 1 antwoord
  • 1 heeft dit probleem
  • 1 weergave
  • Laatste antwoord van 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.

Gekozen oplossing

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

Dit antwoord in context lezen 👍 0

Alle antwoorden (1)

more options

Gekozen oplossing

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