Il 02/01/19 17:10, Carsten Schoenert ha scritto:

So if you now encountering issues would mean that you have enabled the
apparmor profile by yourself after the version that is used in the
postinst script or you doing a update from a version prior to this
version. Stretch never had Thunderbird 1:52.5.0-1~deb9u1, the closest
version smaller to that version was 1:52.4.0-1~deb9u1.

I'm positive I've never consciously enabled apparmor myself, though.
I keep logs of all manual changes, with links to documentation, and I have nothing on apparmor in general or thunderbird specifically.

The system is roughly a couple of years old: it went through the "weasel" rebranding and back, then was upgraded to testing at the beginning of november. My father's PC has a similar history and, unsurprisingly, apparmor for thunderbird is enabled also there.


So you maybe need to rethink how AppArmor is intended to help you for
preventing to some things wrong?

Had I enabled it, I would do so :)
Given that I have not, I'll just disable it and be on my way.


If you need more info on the package installation history on my system, I'd be glad to help. If you believe my case is a one-off, you may close the bug because I accept your explanation.


Regards,
Andrea.

Reply via email to