And by the way, just if somebody is still struggling to find where the
"good" error messages (instead of the surprising useful "some font thing
failed"), grep for apparmor in /var/log/kern.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
My solution was to apply this diff:
diff --git a/./etc-apparmor.d-abstractions-fonts
b/etc/apparmor.d/abstractions/fonts
index 45cdf9a..44c54ac 100644
--- a/./etc-apparmor.d-abstractions-fonts
+++ b/etc/apparmor.d/abstractions/fonts
@@ -51,6 +51,8 @@
/usr/local/share/fonts/ r,
I agree that this bug is super confusing: when apparmor prevents evince
from accessing a font (in my case, because of some folders in /usr/share
having been symlinked to a different partition), there is no visible
error message (except "some font thing failed" in the console log) and
the text with
On Sat, Oct 13, 2018 at 06:54:59PM -, bitinerant wrote:
> I appreciate the suggestions, but none quite fit my use case. It's
> really 2 users wanting to share the fonts--one owns them and the other
> has a symlink. If I put them in /usr/local/share/fonts/ then they don't
> get backed up and
Seth--thanks for the helpful details.
I appreciate the suggestions, but none quite fit my use case. It's
really 2 users wanting to share the fonts--one owns them and the other
has a symlink. If I put them in /usr/local/share/fonts/ then they don't
get backed up and can't be modified. I think the
Nearly all the AppArmor rules provided by upstream AppArmor include
'owner' prefixes on files and directories within user home directories.
This is intentional -- for example, the file
includes:
owner @{HOME}/.fonts.conf r,
owner @{HOME}/.fonts/ r,
owner
I have additional information. Within ~/.fonts I have a subfolder
containing some Windows fonts. It seems that if those files are not
OWNED by the user running Evince (even though they are group readable),
then Evince does not display the fonts at all.
I feel this is a bug. At the very least,
Closely related: Bug #793122
--
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/1448778
Title:
Evince fails to display some fonts (some font thing failed)
To manage notifications
I have a number of PDF files which, when opened, display some text but
not others, and show dozens of "some font thing failed" lines in the
terminal. The PDFs appear fine in Firefox. I don't know what "texlive"
is, so I'm quite sure I'm not using that, but I do have some fonts in
~/.fonts
Thanks
I am using 17.04 and don't have texlive installed or any fonts in
/usr/local. But still this happened. Needed to use `sudo aa-complain
evince`
And yes, "some font thing failed" is an worst kind of debug info I've
seen.
--
You received this bug notification because you are a member of Ubuntu
Just to add a note: it happened to me also, because I have /usr/local as
a symlink to /home/local (in a different partition) and evince (or
apparmor) correctly complained.
So all fonts from Microsoft, which are installed in /usr/local/font,
came out blank.
Setting aa-complain solved momentarily
** Tags added: 15.10
--
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/1448778
Title:
Evince fails to display some fonts (some font thing failed)
To manage notifications about this
thanks for your bug report
reading your kernel log, it seems you have /usr/local installed fonts
/usr/local/texlive/2014/texmf-dist/fonts/opentype/public/tex-gyre/texgyreheros-regular.otf
the issue seems similar to bug #846639 which has been closed because
having custom texlive installation is
The screenshot of the pdf document in okular
** Attachment added: theory_scalar_okular.jpg
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1448778/+attachment/4385016/+files/theory_scalar_okular.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
It seems to be because of some apparmor configuration. After disabling
apparmor for evince, the pdf loads fine.
I guess it's because I have texlive installed and evince tries to load
the fonts from here. Maybe the default configuration for the evince
profile should be more permissive?
--
You
15 matches
Mail list logo
