This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Thunderbird flatpak not loading profile after reboot and impossible to import profile

  • 1 èsì
  • 0 ní àwọn ìṣòro yìí
  • 1 view
  • Èsì tí ó kẹ́hìn lọ́wọ́ qgsgiljyxzgtslsyrz

more options
    1. What Happens

Everything worked fine. Computer simply shut off due to low battery. I rebooted, and when I opened Thunderbird flatpak version 115.1.1 (thunderbird-flatpak - 1.0), the "set up account" screen showed up with none of my previous settings and accounts.

    1. What I Tried

I tried importing my profile manually, but in the console it gives the following error: ``` Uncaught (in promise) DOMException: Could not open the file at /home/user/.var/app/org.mozilla.Thunderbird/.thunderbird/prefs.js ```

I tried importing both `~/.thunderbird` and `~/.var/app/org.mozilla.Thunderbird/.thunderbird` and it gave the same error.

Then, I tried moving all my data from `~/.thunderbird` to a `~/thunderbird-backup` folder, create a new profile *fake* in with the thunderbird "set up account" screen, delete the data it just created in the new `~/.thunderbird` profile, and finally move back in my data from `/thunderbird-backup`.

Now the error `Uncaught (in promise) DOMException` does not show up anymore. However, it does not resolve the issue.

It looks like the import operation works fine, as it tells me it is finished and that it needs to reboot. However, when it reboots, it comes back again with the same "set up account" screen, and none of my data is on there.

Any idea what’s going on? Also, why are there two `.thunderbird/` folder with profiles in it (one in `~/.thunderbird` and one in `~/.var/app/org.mozilla.Thunderbird/.thunderbird`)? Is it part of the problem?

## What Happens Everything worked fine. Computer simply shut off due to low battery. I rebooted, and when I opened Thunderbird flatpak version 115.1.1 (thunderbird-flatpak - 1.0), the "set up account" screen showed up with none of my previous settings and accounts. ## What I Tried I tried importing my profile manually, but in the console it gives the following error: ``` Uncaught (in promise) DOMException: Could not open the file at /home/user/.var/app/org.mozilla.Thunderbird/.thunderbird/prefs.js ``` I tried importing both `~/.thunderbird` and `~/.var/app/org.mozilla.Thunderbird/.thunderbird` and it gave the same error. Then, I tried moving all my data from `~/.thunderbird` to a `~/thunderbird-backup` folder, create a new profile *fake* in with the thunderbird "set up account" screen, delete the data it just created in the new `~/.thunderbird` profile, and finally move back in my data from `/thunderbird-backup`. Now the error `Uncaught (in promise) DOMException` does not show up anymore. However, it does not resolve the issue. It looks like the import operation works fine, as it tells me it is finished and that it needs to reboot. However, when it reboots, it comes back again with the same "set up account" screen, and none of my data is on there. Any idea what’s going on? Also, why are there two `.thunderbird/` folder with profiles in it (one in `~/.thunderbird` and one in `~/.var/app/org.mozilla.Thunderbird/.thunderbird`)? Is it part of the problem?

All Replies (1)

more options

The official Thunderbird flatpak stores its profile in ~/.var/app/org.mozilla.Thunderbird/.thunderbird (it doesn't use ~/.thunderbird)

If your profile was in the latter path then you may follow instructions from https://github.com/flathub/org.mozilla.Thunderbird#migration-from-pre-exisiting-non-flatpak-installations

It's also possible that unexpected shutdown caused some profile corruption.