Hello Phillip, Am 26.11.19 um 09:40 schrieb Philipp Pilhofer: ... > 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 ...?
the magic is quite simple, if the installation is a new installation and the version is greater than 1:52.5.0-1~ don't modify the installation and leave the TB AA profile disabled. If the above is not given than disable the AA profile. And further that means that a user is doing an update and the profiles was active it will also be activated after the installation of the newer version. It was added / modified by this commit https://salsa.debian.org/mozilla-team/thunderbird/commit/81a8c00dc530c7dedf83c9857b227c3c3c164e22 It helps nothing if we all do some some wild guessing, someone has to proof if something is broken in case the user is doing a dist-upgrade from stretch to buster. It's also possible that AppArmor is doing some special in case of a dist-upgrade. The versions are different between the releases. -- Regards Carsten Schoenert
