Closed Bug 1617284 Opened 4 years ago Closed 4 years ago

windows 10 start application with shared profile fails after update to 68.5.0 on fedora

Categories

(Thunderbird :: OS Integration, defect)

Unspecified
Windows 10
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: ekw457, Unassigned)

References

Details

environment: dual boot windows 10 and fedora 31
windows has Thunderbird 68.4.2
fedora has Thunderbird is 68.4.1
Both Thunderbird applications using the same profile on a data
partition (ntfs)
/mnt/my_data_drive/Thunderbird/profile

I installed an update in Fedora for a new version of Thunderbird (68.5.0)
I was able to access and use the shared Thunderbird profile on fedora.

When I started windows and try to start Thunderbird, A window pops up saying:

"A newer version of Thunderbird may have made changes to you profile which are
no longer compatibles with this older version. Use this profile only with that
newer version, or create a new profile for this installation of Thunderbird."

So I updated windows Thunderbird to 68.5.0.
I still get the window message above.

I then reinstalled the prior version of Thunderbird on Fedora.

I can now access and use the shared profile on both systems.

So I tried again, this time Windows Thunderbird is at 68.5.0.
When I install the Thunderbird 68.5.0 on fedora, which works fine, Then I
reboot and try to start Thunderbird on windows , I still get the message above, even though both Thunderbird installations are 68.5.0.
I created a new profile, set up all email accounts, which worked, using the
default profile on windows.
Using the -P option on start I tried to access the shared profile.
I still cannot access my shared folder with the Thunderbird on Windows.
Thunderbird on fedora at 68.5.0 can access the shared profile.

Is there a way to use a shared profile on windows 10 after updating Thunderbird to 68.5.0 on fedora.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID

But ultimately you may get into trouble with bug 653389

See Also: → 653389
You need to log in before you can comment on or make changes to this bug.