Closed Bug 1973153 Opened 2 months ago Closed 2 months ago

Migration from ESR to Release channel failed on macOS case-sensitive file system

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 139
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1971216

People

(Reporter: nad, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.5 Safari/605.1.15

Steps to reproduce:

Installed Thunderbird Release channel on macOS system with existing ESR release installation. Launching the new Thunderbird failed to find previous profile (settings, erc.). The macOS system is installed on a case-sensitive APFS file system rather than a default case-insensitive one.

Migrating from 128.11.0esr (20250522210530) to 139.0.2 (20250606205843)

Actual results:

Searching in ~/Library, I discovered that the new Thunderbird from the release channel had created and was searching in ~/Library/thunderbird (lower-case T) whereas the previous profile from the ESR version was located in ~/Library/Thunderbird (upper-case T). On default case-insensitive macOS file systems this would not be noticed but it does make a difference on case-sensitive installations.

Expected results:

The workaround is to delete ~/Library/thunderbird and either create a symlink from ~/Library/Thunderbird or rename ~/Library/Thunderbird to ~/Library/thunderbird. With that done and relaunching Thunderbird, the old profile was found and Thunderbird behaved as expected.

That's been back to uppercase, effective from TB 140, see bug 1971216.

@ned-daily, thanks for reporting this. Please let us know if there are any issues once 140 is available.

Status: UNCONFIRMED → RESOLVED
Closed: 2 months ago
Duplicate of bug: 1971216
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.