On Wed, Oct 23, 2019 at 06:20:46PM -0400, Nathan Stratton Treadway wrote:
> On Wed, Oct 23, 2019 at 08:27:33 +0100, Chris Green wrote:
> > On Tue, Oct 22, 2019 at 05:43:18PM -0400, Nathan Stratton Treadway wrote:
> > >
> > > It looks like even with the apparmor package purged you could run
> > >
On Wed, Oct 23, 2019 at 08:27:33 +0100, Chris Green wrote:
> On Tue, Oct 22, 2019 at 05:43:18PM -0400, Nathan Stratton Treadway wrote:
> >
> > It looks like even with the apparmor package purged you could run
> > $ sudo cat /sys/kernel/security/apparmor/profiles
> > to see if in fact Apparmor p
On Tue, Oct 22, 2019 at 05:43:18PM -0400, Nathan Stratton Treadway wrote:
>
> It looks like even with the apparmor package purged you could run
> $ sudo cat /sys/kernel/security/apparmor/profiles
> to see if in fact Apparmor profiles are still loaded.
>
>
root@t470:~# cat /sys/kernel/security
On Mon, Oct 21, 2019 at 20:33:35 +0100, Chris Green wrote:
> 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.
I agree that you'd think rebooting the machine aft
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?
>
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 secu
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
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
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
$libre
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 c
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.
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 a
Please, could you purged apparmor and restarted the system? I think you
have uninstalled the program, but, his symptoms continued.
Em dom, 20 de out de 2019 15:04, Chris Green escreveu:
> On Sun, Oct 20, 2019 at 02:02:15PM +0100, Nuno Silva wrote:
> >
> I just removed apparmor from one of my sys
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 d
On Sun, Oct 20, 2019 at 02:02:15PM +0100, Nuno Silva wrote:
> On 2019-10-20, Chris Green wrote:
>
> > On Sun, Oct 20, 2019 at 11:01:02AM +0200, Matthias Apitz wrote:
> >> El día domingo, octubre 20, 2019 a las 09:25:46a. m. +0100, Nuno Silva
> >> escribió:
> >>
> >> > On 2019-10-19, José María M
On 20/10/19 at 12:33, Marcelo Laia wrote:
> On 20/10/19 at 03:05, Nuno Silva wrote:
>
> > Does "grep -R mutt /etc/apparmor.d/" return anything?
>
> root@marcelo:~# grep -R mutt /etc/apparmor.d/
> /etc/apparmor.d/abstractions/private-files: deny @{HOME}/.mutt** mrwkl,
If I comment that line in
On 20/10/19 at 03:05, Nuno Silva wrote:
> Does "grep -R mutt /etc/apparmor.d/" return anything?
root@marcelo:~# grep -R mutt /etc/apparmor.d/
/etc/apparmor.d/abstractions/wayland: owner
/run/user/*/{mesa,mutter,sdl,wayland-cursor,weston,xwayland}-shared-* rw,
/etc/apparmor.d/abstractions/X: ow
On Sun, 20 Oct 2019 15:05:24 +0100 (Nuno Silva)
wrote:
> Does "grep -R mutt /etc/apparmor.d/" return anything?
>
> I suspect that, in a system with this issue, the problematic rule would
> be in abstractions/private-files, and usr.bin.evince includes
> abstractions/evince[1] which includes abstra
On 2019-10-20, Marcelo Laia wrote:
> On 20/10/19 at 02:02, Nuno Silva 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.
>
>
> Bingo
>
> root@marcelo:~# dpkg -l apparmor
> Desired=Unknown/In
On 2019-10-20, José María Mateos wrote:
> On Sun, 20 Oct 2019 10:15:34 -0300 Marcelo Laia
> wrote:
>> root@marcelo:~# dpkg -l apparmor
>> Desired=Unknown/Install/Remove/Purge/Hold
>> |
>> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>> |/ Err?=(none)/Reinst-require
On Sun, 20 Oct 2019 10:15:34 -0300 Marcelo Laia
wrote:
> root@marcelo:~# dpkg -l apparmor
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/
> Nome
On 20/10/19 at 02:02, Nuno Silva 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.
Bingo
root@marcelo:~# dpkg -l apparmor
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-file
On 20/10/19 at 09:25, Nuno Silva wrote:
> Any chance this is the same issue Marcelo Laia reported earlier this
> year?
Yea This is the same! Thank you very much!
If I start to open any doc (ods, xls, doc, odt, pdf) from mutt, this problem
occurs!
To pdf, I am using xpdf, that run out the bo
On 2019-10-20, Chris Green wrote:
> On Sun, Oct 20, 2019 at 11:01:02AM +0200, Matthias Apitz wrote:
>> El día domingo, octubre 20, 2019 a las 09:25:46a. m. +0100, Nuno Silva
>> escribió:
>>
>> > On 2019-10-19, José María Mateos wrote:
>> >
>> > > On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green
On Sun, 20 Oct 2019 09:43:51 +0100 Chris Green wrote:
> Thanks for trying it José, what version of evince are you running?
> Mine is "GNOME Document Viewer 3.32.0".
I'm running 3.18.2 on an Ubuntu Mate 16.04 with Xfce as a desktop
manager.
Cheers,
--
José María (Chema) Mateos || https://rinzew
On Sun, Oct 20, 2019 at 11:01:02AM +0200, Matthias Apitz wrote:
> El día domingo, octubre 20, 2019 a las 09:25:46a. m. +0100, Nuno Silva
> escribió:
>
> > On 2019-10-19, José María Mateos wrote:
> >
> > > On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green wrote:
> > >> Running 'evince ~/.mitt/fred.
El día domingo, octubre 20, 2019 a las 09:25:46a. m. +0100, Nuno Silva escribió:
> On 2019-10-19, José María Mateos wrote:
>
> > On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green wrote:
> >> Running 'evince ~/.mitt/fred.pdf' displays the PDF file successfully
> >> but running 'evince ~/.mutt/fred.p
On Sun, Oct 20, 2019 at 09:25:46AM +0100, Nuno Silva wrote:
> On 2019-10-19, José María Mateos wrote:
>
> > On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green wrote:
> >> Running 'evince ~/.mitt/fred.pdf' displays the PDF file successfully
> >> but running 'evince ~/.mutt/fred.pdf' produces a Permiss
On Sat, Oct 19, 2019 at 05:36:52PM -0400, José María Mateos wrote:
> On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green wrote:
> > Running 'evince ~/.mitt/fred.pdf' displays the PDF file successfully
> > but running 'evince ~/.mutt/fred.pdf' produces a Permission Denied
> > message in a pop-up window.
On 2019-10-19, José María Mateos wrote:
> On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green wrote:
>> Running 'evince ~/.mitt/fred.pdf' displays the PDF file successfully
>> but running 'evince ~/.mutt/fred.pdf' produces a Permission Denied
>> message in a pop-up window. All directory names I have
On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green wrote:
> Running 'evince ~/.mitt/fred.pdf' displays the PDF file successfully
> but running 'evince ~/.mutt/fred.pdf' produces a Permission Denied
> message in a pop-up window. All directory names I have tried other
> than .mutt allow the PDF file to
31 matches
Mail list logo
