Henning Follmann <hfollm...@itcfollmann.com> writes: > On Fri, Aug 07, 2020 at 12:48:19PM +0100, Brian wrote: >> On Fri 07 Aug 2020 at 07:32:12 -0400, Greg Wooledge wrote: >> >> > On Thu, Aug 06, 2020 at 08:16:14PM -0400, Henning Follmann wrote: >> > > Aug 06 19:55:20 typer audit[4039]: AVC apparmor="DENIED" >> > > operation="open" profile="/usr/lib/telepathy/telepathy-*" >> > > name="/usr/share/perl/5.28.1/strict.pm" pid=4039 >> > > comm="telepathy-haze" requested_mask="r" denied >> > >> > > honestly it looks like apparmor is preventing a perl script to execute. >> > >> > I agree. >> > >> > > I guess I should report this. Is the apparmor the right place to report? >> > >> > The right place would be whichever package contains the AppArmor >> > profile. I'm guessing that's some package with "telepathy" in its >> > name. >> >> A very useful page to read is >> >> https://wiki.debian.org/AppArmor/Reportbug >> > > Thanks for the link. > So I went down the rabbit hole and read it. After Greg's answer I am > now a bit more confused. If I understood the AppArmor-ReportBug website > correctly it should be reported against apparmor. But then who will > update the profile in the telepathy package? >
The page says you need to report the bug to whichever package ships the apparmor profile. In this case, that happens to be telepathy-mission-control-5 (https://packages.debian.org/buster/amd64/telepathy-mission-control-5/filelist) with the additional usertags as described on the wiki page. -- regards, kushal
