Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #225954 > unrolled thread

AppArmor or Telepathy error

Started byHenning Follmann <hfollmann@itcfollmann.com>
First post2020-08-07 02:20 +0200
Last post2020-08-07 19:20 +0200
Articles 6 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  AppArmor or Telepathy error Henning Follmann <hfollmann@itcfollmann.com> - 2020-08-07 02:20 +0200
    Re: AppArmor or Telepathy error Greg Wooledge <wooledg@eeg.ccf.org> - 2020-08-07 13:40 +0200
      Re: AppArmor or Telepathy error Brian <ad44@cityscape.co.uk> - 2020-08-07 14:40 +0200
        Re: AppArmor or Telepathy error Henning Follmann <hfollmann@itcfollmann.com> - 2020-08-07 17:00 +0200
          Re: AppArmor or Telepathy error Kushal Kumaran <kushal@locationd.net> - 2020-08-07 17:20 +0200
            Re: AppArmor or Telepathy error Brian <ad44@cityscape.co.uk> - 2020-08-07 19:20 +0200

#225954 — AppArmor or Telepathy error

FromHenning Follmann <hfollmann@itcfollmann.com>
Date2020-08-07 02:20 +0200
SubjectAppArmor or Telepathy error
Message-ID<AAYh3-lM-1@gated-at.bofh.it>
I tried today Empathy for the first time.
And I was not able to connect to my jabber server. So
i dug a bit deeper, but honestly I really do not understand this:

**** log ****
Aug 06 19:55:19 typer dbus-daemon[3320]: [session uid=1000 pid=3320] Activating service name='org.freedesktop.Telepathy.ConnectionManager.haze' requested by ':1.66' (uid=1000 pid=4031 comm="/usr/bin/empathy-acco
Aug 06 19:55:19 typer tracker-miner-f[3591]: Could not process 'file:///home/henning/%2318875467': Error when getting information for file “/home/henning/#18875467”: No such file or directory
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
Aug 06 19:55:20 typer org.freedesktop.Telepathy.ConnectionManager.haze[3320]: Can't locate strict.pm:   /usr/share/perl/5.28/strict.pm: Permission denied at /usr/lib/purple-2/XEP-0027.pl line 31.
Aug 06 19:55:20 typer org.freedesktop.Telepathy.ConnectionManager.haze[3320]: BEGIN failed--compilation aborted at /usr/lib/purple-2/XEP-0027.pl line 31.
Aug 06 19:55:20 typer kernel: audit: type=1400 audit(1596758120.240:27): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/telepathy-*" name="/usr/share/perl/5.28.1/strict.pm" pid=4039 comm="telepat
Aug 06 19:55:20 typer dbus-daemon[3320]: [session uid=1000 pid=3320] Successfully activated service 'org.freedesktop.Telepathy.ConnectionManager.haze'

*************

honestly it looks like apparmor is preventing a perl script to execute.

I guess I should report this. Is the apparmor the right place to report?


-H


-- 
Henning Follmann           | hfollmann@itcfollmann.com

[toc] | [next] | [standalone]

#225971

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2020-08-07 13:40 +0200
Message-ID<AB8T8-6KZ-23@gated-at.bofh.it>
In reply to#225954
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.

[toc] | [prev] | [next] | [standalone]

#225974

FromBrian <ad44@cityscape.co.uk>
Date2020-08-07 14:40 +0200
Message-ID<AB9Pc-7jV-19@gated-at.bofh.it>
In reply to#225971
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

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#225976

FromHenning Follmann <hfollmann@itcfollmann.com>
Date2020-08-07 17:00 +0200
Message-ID<ABc0K-7D-63@gated-at.bofh.it>
In reply to#225974
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?

-H



-- 
Henning Follmann           | hfollmann@itcfollmann.com

[toc] | [prev] | [next] | [standalone]

#225979

FromKushal Kumaran <kushal@locationd.net>
Date2020-08-07 17:20 +0200
Message-ID<ABck2-tS-7@gated-at.bofh.it>
In reply to#225976
Henning Follmann <hfollmann@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

[toc] | [prev] | [next] | [standalone]

#225987

FromBrian <ad44@cityscape.co.uk>
Date2020-08-07 19:20 +0200
Message-ID<ABeca-1Ce-13@gated-at.bofh.it>
In reply to#225979
On Fri 07 Aug 2020 at 08:11:12 -0700, Kushal Kumaran wrote:

> Henning Follmann <hfollmann@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.

Indeed.

It is also useful  to appreciate that the apparmor team is generally
very responsive to bug reports. At least, that is my experience.

-- 
Brian.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web