[pkg-apparmor] Bug#935058: Bug#935058: torbrowser-launcher: Fails to start because apparmor prevents acces to mutter/xwayland xauth file

[Jamie Strandboge]

On Mon, 19 Aug 2019, intrigeri wrote:

> > torbrowser-launcher fails to start with this apparmor message in kernel log:
> 
> > [  135.043787] audit: type=1400 audit(1566153604.771:58): apparmor="DENIED"
> > operation="open" profile="torbrowser_firefox" name="/run/user/1000/.mutter-
> > Xwaylandauth.B4GI6Z" pid=4793 comm="firefox.real" requested_mask="r"
> > denied_mask="r" fsuid=1000 ouid=1000
> 
> > This happens when starting torbrowser-launcher in a GNOME Wayland session with
> > Mutter 3.33.90-2 from Experimental.
> 
> Oh, interesting, good catch! I did not know that this new version of
> GNOME changed the path to this Xwayland thing. I'm very glad you
> spotted this, thanks! :)
> 
> I believe this needs to be fixed in
> /etc/apparmor.d/abstractions/wayland, thus reassigning. I'll prepare
> a merge request upstream and will fix this in Debian ASAP.
> 

IME this should be fixed in the X abstraction since the path is for
Xwayland, an X server (that talks to wayland).

-- 
Jamie Strandboge             | http://www.canonical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-apparmor-team/attachments/20190820/eb4fa792/attachment-0001.sig>