Bug#904164: Text of some PDF invisible: some font thing failed
Jason Crain
jason at inspiresomeone.us
Mon Jul 23 00:52:20 BST 2018
On Sun, Jul 22, 2018 at 10:57:24PM +0200, Mathias Brodala wrote:
> Jason Crain schrieb am 21.07.2018 um 20:51:
> > How does it look if you run `pdftocairo -png in.pdf out` to convert to
> > png images? pdftocairo is in the poppler-utils package. Evince uses
> > poppler for PDF rendering so that should get the same result as Evince.
>
> Seems like there is something off, when I do that I get the following:
>
> I/O Error: Cannot open '/root/.fonts/verdana.ttf'
> Syntax Error: failed to load truetype font<0a>
> some font thing failed
>
> This is repeated at lot of times for "arial.ttf", "verdana.ttf" and
> "verdanab.ttf".
>
> I have no idea why Evince/poppler suddenly thinks these fonts reside in
> /root/.fonts. They always where in /home/<user>/.fonts and I cannot remember
> the last time I ever changed something about this.
Poppler uses fontconfig to locate fonts so it sounds like there's
something wrong with fontconfig instead of poppler or evince.
There's a few things you can try like using `fc-cat -v` to inspect the
cache files or `fc-cache -f` to rebuild the cache.
More information about the pkg-gnome-maintainers
mailing list