On Mon, Oct 21, 2019 at 02:19:25PM +0100, Nuno Silva wrote:
> On 2019-10-21, Chris Green wrote:
>
> > On Sun, Oct 20, 2019 at 05:08:01PM -0400, Nathan Stratton Treadway wrote:
> >> On Sun, Oct 20, 2019 at 18:04:05 +0100, Chris Green wrote:
> >> > I just removed apparmor from one of my systems (I can see no use for
> >> > it anyway), I still get the error with evince.
> >>
> >> I'm not using Ubuntu 19.04 myself and so can't say whether or not your
> >> problem is caused by Apparmor, but if you just did "apt-get remove
> >> apparmor" to remove the package, I'm not sure that operation actually
> >> disables Apparmor enforcement.
> >>
> > Well, I did "apt purge apparmor" and I also removed two other packages
> > with apparmor in the name.
> >
> >
> >> (That is, at least on my Bionic/18.04 system, with a quick look through
> >> the /var/lib/dpkg/info/apparmor.{pre,post}rm scripts I'm not seeing
> >> seeing any logic to turn off enforcement during a package-remove
> >> operation.)
> >>
> >> So, you may still want to look closely in your system log files to see
> >> if there are any Apparmor access-denied messages, just in case removing
> >> the package isn't enough to eliminate the evince-profile restriction....
> >>
> > No, nothing logged at all but I'm still getting the Permission Denied.
>
> If you did not reboot, apparmor might still be running, try stopping the
> "apparmor" service, see:
> https://help.ubuntu.com/community/AppArmor#Disable_AppArmor_framework
>
I'm pretty sure I rebooted but tried the above anyway:-
root@t470:~# systemctl disable apparmor
Failed to disable unit: Unit file apparmor.service does not exist.
root@t470:~#
I'm still getting Permission Denied from evince. I think apparmor is
ruled out now.
--
Chris Green
