Re: Really strange problem with evince PDF reader and .mutt directory

2019-10-21 Thread Chris Green 
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.

-- 
Chris Green

Re: Really strange problem with evince PDF reader and .mutt directory

2019-10-21 Thread nunojsilva 
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

-- 
Nuno Silva

Re: Really strange problem with evince PDF reader and .mutt directory

2019-10-21 Thread Chris Green 
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

Re: Really strange problem with evince PDF reader and .mutt directory

2019-10-21 Thread Marcelo Laia 
Em seg, 21 de out de 2019 11:22, Chris Green  escreveu:

>
> I'm still getting Permission Denied from evince.  I think apparmor is
> ruled out now.
>

Please, have you tried to open a doc (doc, docx, odt) from ~/.mutt or from
~/.mutt/temp?

For example:

$libreoffice ~/.mutt/yourdoc.odt

or

$libreoffice ~/.mutt/temp/yourdoc.odt

And from mutt? What is the behavior if you try to open a document (doc, docx,
odt) direct from mutt (V+enter in the file name)?

Have you Em seg, 21 de out de 2019 11:22, Chris Green  escreveu:
I'm still getting Permission Denied from evince.  I think apparmor is
ruled out now.

Re: Really strange problem with evince PDF reader and .mutt directory

2019-10-21 Thread Chris Green 
On Mon, Oct 21, 2019 at 12:33:37PM -0300, Marcelo Laia wrote:
> Em seg, 21 de out de 2019 11:22, Chris Green  escreveu:
> 
> >
> > I'm still getting Permission Denied from evince.  I think apparmor is
> > ruled out now.
> >
> 
> Please, have you tried to open a doc (doc, docx, odt) from ~/.mutt or from
> ~/.mutt/temp?
> 
> For example:
> 
> $libreoffice ~/.mutt/yourdoc.odt
> 
> or
> 
> $libreoffice ~/.mutt/temp/yourdoc.odt
> 
No problem, I can open a .doc file in ~/.mutt.

> And from mutt? What is the behavior if you try to open a document (doc, docx,
> odt) direct from mutt (V+enter in the file name)?
> 
I'll try it next.

-- 
Chris Green

Re: Really strange problem with evince PDF reader and .mutt directory

2019-10-21 Thread Derek Martin 
On Sun, Oct 20, 2019 at 06:04:05PM +0100, Chris Green wrote:
> On Sun, Oct 20, 2019 at 02:02:15PM +0100, Nuno Silva wrote:
> > On 2019-10-20, Chris Green wrote:
> > Do these systems have apparmor? It seems to be some sort of security
> > tool which restricts access to files and directories based on rules.
> > 
> > I don't use ubuntu (or ubuntu-based) systems nor apparmor, but this
> > looks like it might be related:
> > 
> > https://gitlab.com/apparmor/apparmor/raw/master/profiles/apparmor.d/abstractions/private-files
> > 
> I just removed apparmor from one of my systems (I can see no use for
> it anyway), I still get the error with evince.

But did you reboot or otherwise confirm that apparmor is not still
in play?  I'm not super familiar with it but it appears to be a kernel
module--if it were loaded I would expect it to stay that way despite
the file being removed... at least until the kernel was restarted
(i.e. you rebooted the machine).  Though, it's possible that removing
the package asks the kernel to unload the module.

-- 
Derek D. Martinhttp://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.



signature.asc
Description: PGP signature

Re: Really strange problem with evince PDF reader and .mutt directory

2019-10-21 Thread Chris Green 
On Mon, Oct 21, 2019 at 12:49:10PM -0500, Derek Martin wrote:
> On Sun, Oct 20, 2019 at 06:04:05PM +0100, Chris Green wrote:
> > On Sun, Oct 20, 2019 at 02:02:15PM +0100, Nuno Silva wrote:
> > > On 2019-10-20, Chris Green wrote:
> > > Do these systems have apparmor? It seems to be some sort of security
> > > tool which restricts access to files and directories based on rules.
> > > 
> > > I don't use ubuntu (or ubuntu-based) systems nor apparmor, but this
> > > looks like it might be related:
> > > 
> > > https://gitlab.com/apparmor/apparmor/raw/master/profiles/apparmor.d/abstractions/private-files
> > > 
> > I just removed apparmor from one of my systems (I can see no use for
> > it anyway), I still get the error with evince.
> 
> But did you reboot or otherwise confirm that apparmor is not still
> in play?  I'm not super familiar with it but it appears to be a kernel
> module--if it were loaded I would expect it to stay that way despite
> the file being removed... at least until the kernel was restarted
> (i.e. you rebooted the machine).  Though, it's possible that removing
> the package asks the kernel to unload the module.
> 
I removed the apparmor package, and I stopped it using systemd, and I
rebooted the machine.  I still have the error with evince, so I'm
pretty convinced it's not to do with apparmor.


-- 
Chris Green

Re: Really strange problem with evince PDF reader and .mutt directory

2019-10-21 Thread Marcelo Laia 
Em seg, 21 de out de 2019 16:33, Chris Green  escreveu:

>
> I'm
> pretty convinced it's not to do with apparmor.
>


Does "grep -R mutt /etc/apparmor.d/" return anything?

>