Closed Bug 1611816 Opened 5 years ago Closed 4 years ago

Updating to 68.4.2 from 52.9.0 ==> profile and all settings lost

Categories

(Thunderbird :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1590036

People

(Reporter: breite_gu, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

Followed Thunderbird Update suggestion ...

Actual results:

Connection to old profile and settings is not re-established / re-connected
e-mail / filters / folders / rules disappear

Expected results:

The old data should be there ... / imported
(which they are after removing 68.4.2 and reinstalling 52.9.0)

Not sure about: My >> jNNNabcd.default << file is located on a different HD, from where Thunderbird is installed, possibly causing this.

However, at least a warning should be advised (if not handled automatically).

You probably installed the new version in another folder?
If you start thunderbird with "thunderbird.exe -P" you can select the old profile from the profile manager

Component: Untriaged → General

No, I did not install into another folder.
I merely followed Thunderbird "Update Channel".
It is the update itself which does not recognize the "old-profile" - location.
Nevertheless, even a non-standard location could be determined prior to installing an update.
I still believe that the update routine should contain a warning / hint in this regard.

  • Users may have to restore their old profiles by following the approach you indicated.

We're working on that in bug 1590036.

Hi there,
Yesterday 03 to 04 Feb 2020 it happened again.
Thunderbird (auto) update, profile and all settings lost.
Back to square one ...

See Also: → 1612414

(In reply to breite_gu from comment #4)

Hi there,
Yesterday 03 to 04 Feb 2020 it happened again.
Thunderbird (auto) update, profile and all settings lost.
Back to square one ...

bug 1590036 was fixed in 68.6.0 in March 2020, so your problem should have stopped at that time

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.