registry team mailing list archive

Thread
Date

[Bug 571725] Re: evince not open

To: registry@xxxxxxxxxxxxxxxxxxx
From: gfairbanks <elvis-launchpad@xxxxxxxxxxxxx>
Date: Fri, 04 Jun 2010 15:14:08 -0000
Reply-to: Bug 571725 <571725@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This is a comment to help others who have similar issues.  I had moved
my home directory to /opt/home/george on a different partition.
AppArmor appears to prevent evince from writing there.  I edited my
/etc/apparmor.d/tunables/home file (see
https://wiki.ubuntu.com/DebuggingApparmor#Adjusting%20Tunables) from:

@{HOMEDIRS}=/home/

to

@{HOMEDIRS}=/home/ /opt/home/george/

Then restarted apparmor

sudo /etc/init.d/apparmor restart

My evince problems (similar to reported above) are gone.  Specifically,
it no longer complains about not being able to read/write ~/.recently-
used.xbel, ~/.gnome2/evince/evince_toolbar.xml, and
~/.gnome2/evince/evince_toolbar.xml.  And it retains my settings across
sessions.

-- 
evince not open
https://bugs.launchpad.net/bugs/571725
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Fedora.