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

Profile is not loaded after migration from another Ubuntu machine, folders are correct

  • 1 reply
  • 1 has this problem
  • 18 views
  • Last reply by Wollipolli

more options

I have migrated my profile for Thunderbird (TB) from an old machine to a new machine, both running Ubuntu 20.04.4LTS. Both have TB 91.7.0 installed via apt. The Profile folders are located on a separate NTFS partition. I opened a terminal and ran "thunderbird -p" to open the profile manager. I created a new profile and pointed it to the profile folder path (path/to/ntfs/partition/Thunderbird/Profiles/xxxxxxxxx.default).

I open TB but only see the "welcome page" asking me to setup a new account. When I check the profile folder under about:profiles it shows me the correct path.

What could be the issue? I appreciate your help!

For migrating Firefox everything worked smoothly using the same procedure.

I have migrated my profile for Thunderbird (TB) from an old machine to a new machine, both running Ubuntu 20.04.4LTS. Both have TB 91.7.0 installed via apt. The Profile folders are located on a separate NTFS partition. I opened a terminal and ran "thunderbird -p" to open the profile manager. I created a new profile and pointed it to the profile folder path (path/to/ntfs/partition/Thunderbird/Profiles/xxxxxxxxx.default). I open TB but only see the "welcome page" asking me to setup a new account. When I check the profile folder under about:profiles it shows me the correct path. What could be the issue? I appreciate your help! For migrating Firefox everything worked smoothly using the same procedure.

Chosen solution

In a desperate attempt, I redid the whole migration and this time it worked. The copy of the profile folder must have been corrupted or else I don't understand.

Issue can be closed...

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

In a desperate attempt, I redid the whole migration and this time it worked. The copy of the profile folder must have been corrupted or else I don't understand.

Issue can be closed...