Closed Bug 1769245 Opened 2 years ago Closed 2 years ago

autoupdate to 91.9.0 x86 version all existed email boxes was not migrated

Categories

(Thunderbird :: Installer, defect)

Thunderbird 99
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: maxim.zayarnyuk, Unassigned)

Details

(Keywords: dataloss)

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

Steps to reproduce:

Use prev. version with autoupdate emabled;
have 3 email boxes; (all imap)
have addons 'duplicate messages remove' and 'google calendar connect';
then appears latest autoupdate and app closed/started

Actual results:

all boxes disappears; (was not able to readd in any known way, but looks like data inside profile still exists but thunderbird was not able to display email boxes at all);

Expected results:

it should not corrupt existed email boxes in any way;
at least if it's known issue you must do backup and option for users to rollback and try again; or at least show error if that email boxes had problems with readd etc;

Tried Help | Troubleshoot mode?

tried via 'help'->..'.Troubleshoot', restarted with disabled addons and continue in Troubleshoot mode same result;
tried readd gmail accounts errors;
do bachup of roaming and tried beta 'Thunderbird Setup 101.0b1.exe' - same and mot able to add gmail accounts;

in the end decided is waste of time and found old version of app
Thunderbird_Setup_78.10.1.exe (- x64)
removed 'roaming thund.' folder and readd accounts without problesm; wait a lot and redownloaded all messages 11.2 Gb (I am not use a lot of address book so it was not a problem, calendar will integrate later;)
then do backup and tried apply app updates - it go to ..78.40... first and then to latest 91.9 x64 without problems that time;
__
so maybe problem is prev. version was x86;
or maybe some updates between ..78.40... - and - 91.9 that was autoapplyed before;
or some addon ('duplicate remover' or 'google calendar connector') but it most strange if that related;

Ok, I think we'll never find out what happened.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Keywords: dataloss

I think what happened is clear, the profile per install did its usual thing and decided the user needed a new profile. This is exactly the thinkg I have need complaining about for years now.

Without any warning notification or a "hey I think your existing profile should not be used with this update. What do you think?" The user gets dropped into the new account wizard. This has been going on since V68 was released and so far thee have been some mitigations, Jorg did good work on this subject. However, no one is addressing the appalling lack of information to the user, or a simple GUI based recovery. No user should be expected to use command line arguments. Users expect to click a mouse and perhaps drag with their finger. Most do not even know there is a command line to work with, let alone how to use it!

If you want the feature, and you have made it clear you think it is a good thing. At least offer the users a method of recovery for the regular failures which result in inordinate levels of user support requests because the update broke something for no good reason. This is worse than an addon incompatibility. Thunderbird is not capable of updating itself without making a mess of existing profiles in a small percentage of cases and after 3 years it is still the disaster it was with the release of V68. Little has changed, except folk who lose their profile sometime manage to recover it, using the command line. Sometimes they decide to find a mail client they think they can rely on to manage their mail.

Mostly these issue have to do with 32 Vs 64 installs I think, because the stupid algorithm uses the installation directory as part of the "per install" logic and windows uses different directories for 64 and 32 bit installations. Ipso facto the change is a "per version" install. How quaint as they say. The users do not think so and neither do I.

You need to log in before you can comment on or make changes to this bug.