Am 26.11.19 um 19:51 schrieb Carsten Schoenert: > 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 >
I do not understand that code completely, but if it does what you say it should be all fine. > 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. > Yap, sorry for my wild guessing ... it definitely is weird, as I upgraded two (or three?) machines with more or less the same configuration (tb profile "somewhere else") and it happened only in one case IIRC. Best wishes, Philipp
