Thanks Scott for the feedback. This rule:
/usr/local/texlive/2013/texmf-dist/fonts/** r,
is not really something we'll add to the shipped profile because it is
site specific. However, this rule can be added to
/etc/apparmor.d/local/usr.bin.evince, which is intended for site-
specific
I can reproduce this bug by trying to open the pdf failing.pdf (posted
earlier). Note that it appears fine to my eyes but the error messages to
STDERR and the apparmor entries in kern.log show that there is a
problem. It must be that the problem font is just not used in many parts
of this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evince (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
With my document (a tax document I'd rather not share), evince fails to
render the text, showing various odd lines, shadings, etc. in place of
the text. I *think* xpdf renders it correctly for about 3 seconds, and
then crashes. For the few seconds I see it, it appears correct. Adobe
Acrobat Reader
I don't know whose problem it is, but by adding this line in
/etc/apparmor.d/usr.bin.evince, in section for /usr/bin/evince, it seems
to be solved. Of course, you need to replace the directory with the one
containing your files...
# Fonts, stow, WTF??? nickie
Thanks Dennis. Your changes indicate that apparmor is not the main
problem (though it was certainly blocking you at first :). Unassigning
myself so someone from the desktop team can take over.
** Tags removed: apparmor
** Changed in: evince (Ubuntu)
Status: Incomplete = New
** Changed
I did as you suggested (the file was indeed all comments), but it didn't
remedy the problem. I still can't see the body fonts in the failing pdf.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
Dennis, can you post your /var/log/kern.log after making the change?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/888789
Title:
evince doesn't render embedded font
To manage
Sure, here it is. I've clipped the less relevant parts.
** Attachment added: kern.log parts after editing apparmor settings
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/888789/+attachment/2693740/+files/kern.log
--
You received this bug notification because you are a member of
This may be related to apparmor. What are the contents of
/etc/apparmor.d/tunables/home.d/ubuntu? If it is all comments, can you
update it to have:
@{HOMEDIRS}+=/private/home/
Then perform:
$ sudo /etc/init.d/apparmor force-reload
** Changed in: evince (Ubuntu)
Status: New = Incomplete
** Attachment added: stderr of evince when opening the pdf document
https://bugs.launchpad.net/bugs/888789/+attachment/2592526/+files/evince.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
Attached is the document that fails to render.
I've observed the same issue with evince on Ubuntu 10.04.
** Attachment added: a pdf document failing to render correctly in evince
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/888789/+attachment/2592530/+files/failing.pdf
--
You
12 matches
Mail list logo
