![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
Thunderbird flatpak not loading profile after reboot and impossible to import profile
- 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?
Все ответы (1)
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.