GNOME Bugzilla – Bug 328168
unreadable pdf
Last modified: 2006-02-22 00:45:28 UTC
Please describe the problem: opening an ebook of mine, i found it unreadable due to random characters displayed instead of correct ones (see attached screenshot). i tested evince with the docs found in http://live.gnome.org/Evince/Testing and "java lang spec" is having the same problem. Then, closing the application, evince crashes Steps to reproduce: 1. open a pdf 2. check if displayed chars are correct or garbage 3. close evince Actual results: the displayed pdf is unreadable. closing evince causes evince to crash Expected results: having a readble document and no crashes at the end Does this happen every time? it happens with some pdf, can't understand what's wrong with them Other information: i got a gentoo system. here follows some versions: media-libs/tiff-3.7.4 gnome-base/gnome-vfs-2.12.2 gnome-base/libglade-2.5.1 gnome-base/gconf-2.12.1 gnome-base/libgnome-2.12.0.1 gnome-base/libgnomeprintui-2.12.1 gnome-base/libgnomeui-2.12.0 gnome-base/nautilus-2.12.2 x11-libs/gtk+-2.8.10 gnome-base/gnome-keyring-0.4.6 app-text/ghostscript-esp-7.07.1-r10 dev-libs/glib-2.8.5 app-text/poppler-bindings-0.5.0 app-text/poppler-0.5.0 whole system is built with nptl and gcc4.0.2
Created attachment 57849 [details] the displayed java lang spec: wrong chars the pdf was taken from test pdf page
Created attachment 57850 [details] closing evince causes evince to crash closing evince causes evince to crash
Created attachment 57851 [details] a correctly displayed pdf a correctly displayed pdf taken from the test pdf page
Created attachment 57852 [details] evince bug trace evince bug trace
seems to a bug from poppler not from evince with poppler 0.5 they are now using fontconfig to find unembedded fonts probably fontconfig is not always able to correctly find fonts
Should it be the dup of poppler bug 4030?
don't know: i was looking at poppler bug 4064 as long as with correctly viewable pdfs i don't see any output in the console, while i see Error: Couldn't find a font for 'Times Roman' some font thing failed Error: Couldn't find a font for 'Times Italic' some font thing failed Error: Couldn't find a font for 'Times Bold' some font thing failed with docs like the java lang spec. it could even be a misconfiguration of fontconfig, but i don't know and i look further for a reply from poppler devs
yeah, this is definitely related to poppler bug 4030...
That should be the issue described in poppler bug 5758 and I suspect it's fixed already in poppler HEAD, please upgrade. *** This bug has been marked as a duplicate of 328999 ***