The story of this bug is a little bit different from bug #447292 as I have normal (or lazy) setting of Ubuntu 9.10 with my home directory in /home folder.
I have some extra fonts installed which changed file /etc/fonts/font.conf and /etc/fonts/conf.d/. This pushed me to the same issue of this bug.
I checked the apparmor profile for evince, noticed that no permission granted to access the font configuration. I did this to fix this issue in a simple way (although I'm not sure if this will involve any security issues as mentioned in bug #447292)
1. Stop apparmor
sudo /etc/init.d/apparmor stop
2. Modify file /etc/apparmor.d/usr.bin.evince
put this new line underneath line 9 #include <abstractions/evince>
#include <abstractions/fonts>
3. Restart apparmor
sudo /etc/init.d/apparmor start
and the evince boy is back
So the discussion is: shall we prevent evince from font configuration due to security reasons?
The story of this bug is a little bit different from bug #447292 as I have normal (or lazy) setting of Ubuntu 9.10 with my home directory in /home folder.
I have some extra fonts installed which changed file /etc/fonts/ font.conf and /etc/fonts/conf.d/. This pushed me to the same issue of this bug.
I checked the apparmor profile for evince, noticed that no permission granted to access the font configuration. I did this to fix this issue in a simple way (although I'm not sure if this will involve any security issues as mentioned in bug #447292)
1. Stop apparmor d/apparmor stop d/usr.bin. evince evince> fonts> d/apparmor start
sudo /etc/init.
2. Modify file /etc/apparmor.
put this new line underneath line 9 #include <abstractions/
#include <abstractions/
3. Restart apparmor
sudo /etc/init.
and the evince boy is back
So the discussion is: shall we prevent evince from font configuration due to security reasons?
Thanks.