Hello Hansjoerg, Am 25.11.19 um 23:16 schrieb H. Buchberger: > Hi Carsten, > > as my Thunderbird mail profile (not Thunderbird AA profile) was working > well before the upgrade stretch -> buster and did not work any more > after the upgrade, the upgrade must have got something to do with it.
no, we don't touch or modify any data within the /home folders without interacting by the user. The only automatic controlled instance that can make changes to the users profile is the Thunderbird application itself. > 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. > BTW: During my upgrade stretch -> buster Thunderbird (and Firefox) was > also updated (from version 60.9.0 to now 68.2.2) and after that I had to > "downgrade" my Thunderbird mail profile. Also a bit weird. You can't 'downgrade' your mail profile. The only possible and reasonable action would be to replace the existing profile with an backup. But we are going in circles, the truth can be found in the (sys)log. And the root for issue here will be apparmor. See also https://wiki.debian.org/AppArmor/Debug -- Regards Carsten Schoenert