Good morning,
Am 26.11.19 um 08:14 schrieb Carsten Schoenert: >> Unfortunately I don't have a complete back of my system before the >> upgrade. But from the history in this bug report I guess that the AA >> profile was already defined in stretch - probably disabled. >> >> So the upgrade might have removed the "disabled" setting. > > Also here my answer is no, the postinst script for the thunderbird > package has some magic to not enable the AA profile within new > installations. But it will keep an AA profile as active it it was active > before the update. > I certainly did never touch AA, as I did not even know what it is. And after my stretch to buster upgrade, I had to deactivate it manually as tb was not working any more (because of my symlinked tb mail profile, which I of course did not change during the upgrade). I do not know the cause, but it seems obvious that the tb AA profile under some circumstances becomes activated during upgrade process. Everyone posting in this bug issue seems to experience it ... I guess the "magic not to enable the AA profile" does not work always ...? Best wishes, Philipp
