Hi All,
I've been encountering this on my workstation as well, and had some time
to look into it on my system.
Using the advice above, I replaced the deny's in the apparmor profile
with audit deny's, and found the lines that are causing it to not open.
The relevant lines from my dmesg are:
[Thu Dec 7 06:12:33 2017] audit: type=1400 audit(1512648754.135:45):
apparmor="DENIED" operation="open" profile="thunderbird"
name="/home/e/.Xauthority" pid=9223 comm="thunderbird"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
[Thu Dec 7 06:12:33 2017] audit: type=1400 audit(1512648754.135:46):
apparmor="DENIED" operation="open" profile="thunderbird"
name="/home/e/.Xauthority" pid=9238 comm="thunderbird"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Looking into usr.bin.thunderbird, it seems like the line that blocks
.Xauthority is line 113:
deny @{HOME}/.* r
Changing this line to:
deny @{HOME}/.[^X]* r
allows thunderbird to start as normal for me. That likely isn't the best
solution for this file (as I've never really had to deal with apparmor
before, so I don't really know the syntax or options), but it should at
least give you all a starting point.
Hopefully that helps a bit for you all. (also, please excuse if the
formatting of the message is messed up, I've never sent anything to the
debian bug tracker system either).
Thank you,
Eric
