Created attachment 52527 [details] Example PDF PDF made with LaTeX from TeX Live 2011 using DejaVu Sans Mono version 2.33 viewed with evince reports Pango warnings. (evince:4885): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'DejaVu Sans Mono 5.25' (evince:4885): Pango-WARNING **: font_face status is: <unknown error status> (evince:4885): Pango-WARNING **: scaled_font status is: out of memory This can be reproduced with the TeX file below that has to be run through xelatex and viewed with evince from the command line: \documentclass{article} \usepackage{fontspec} \begin{document} \fontspec{DejaVu Sans Mono} asdf \end{document} The Pango warnings appear on the command line. The resulting PDF is also attached to this issue. These errors are new, perhaps something is wrong with the font file. Please investigate and fix.
I opened the PDF file with evince, but I didn't get these errors. It seems to me that it might be an issue related to evince or other software (out of memory warning), not to the dejavu package. I tried the file you sent me and also newly generated file. I use Slackware 12.2 (no Gnome, no evince), so I had to install some version of evince and required packages (taken from an unofficial repository to make it easier). The used versions of possibly relevant programs are: evince 2.24.2 pango 1.20.5 poppler 0.8.5 cairo 1.6.4 I displayed the file also with xpdf, kpdf and epdfview (all from the command line), all without errors. What do you mean with "These errors are new"? Was the error introduced with and update of the dejavu package? What version of the dejavu package do you use (look at the date in changelog)? Can you reproduce the error on other systems with a different version of evince? Do you get the same error if you use pdfTeX or if you create similar PDF with something completely different (such as OpenOffice)? The package dejavu is relatively new and all versions of this package should use exactly the same ttf files (unless I did some error that I'm not aware of).
If was a problem with font config. Clearing out the font config's system cache and user cache solved it.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.