Evince does not display some fonts: "Error: could not create type1 face some font thing failed" - okular, epdfview and zathura also affected by this issue.

Bug #1111429 reported by Michael Mess
40
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Evince
New
Undecided
Unassigned
Fontconfig
New
Undecided
Unassigned
Poppler
New
Undecided
Unassigned
ePDFView
New
Undecided
Unassigned
okular
New
Undecided
Unassigned
epdfview (Ubuntu)
Confirmed
Undecided
Unassigned
evince (Ubuntu)
Fix Released
Undecided
Unassigned
fontconfig (Ubuntu)
Invalid
Undecided
Unassigned
okular (Ubuntu)
Fix Released
Undecided
Unassigned
poppler (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Some documents are displayed incompletely by evince.

evince, okular, epdfview, zathura are also affected by this bug. But mupdf works well.
As multiple applications are likewise affected, it seems to be an issue with a commonly used library.

Some text is missing, but this text can be marked and appears like it would be spaces only, but copy and paste works well and the correct text appears when pasted.
Thus it seems to be a problem displaying the text using the specified font.

In the shell, plenty of error messages appear: "Error: could not create type1 face some font thing failed"

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: evince 3.4.0-0ubuntu1.4
ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
Uname: Linux 3.2.0-36-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Thu Jan 31 13:34:28 2013
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4)
KernLog:

MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Michael Mess (michael-michaelmess) wrote :
Revision history for this message
Michael Mess (michael-michaelmess) wrote :

Attached screenshot showing the bug.

Revision history for this message
Michael Mess (michael-michaelmess) wrote :

The program epdfview is also affected and the document looks similar (There are some coloring differences), thus it seems to be a problem of a commonly used library.

Revision history for this message
Michael Mess (michael-michaelmess) wrote :
Revision history for this message
Michael Mess (michael-michaelmess) wrote :
Revision history for this message
Michael Mess (michael-michaelmess) wrote :

Attached Output of the pdffonts command.

Revision history for this message
Michael Mess (michael-michaelmess) wrote :

Attached screenshot of document correctly displayed by mupdf.

Revision history for this message
madbiologist (me-again) wrote :

This is still occurring on Ubuntu 12.10 "Quantal Quetzal" with evince 3.6.0-0ubuntu2 and poppler 0.20.4-0ubuntu1.1.

tags: added: quantal
Changed in evince (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Mess (michael-michaelmess) wrote :

Testing the file DOSB_Pruefungswegweiser_Komplett_web_11_12.pdf with various pdf viewers listed on http://wiki.ubuntuusers.de/PDF

 * evince: Affected
 * okular: Affected
 * epdfview: Affected
 * firefox: (very slow pdf viewer) Does not work at all
 * mupdf: works
 * xpdf: Crashes with Segmentation fault
 * qpdfview: (not available in Ubuntu 12.04)
 * zathura: Affected

description: updated
description: updated
description: updated
description: updated
Revision history for this message
Michael Mess (michael-michaelmess) wrote :

Created Bug for xpdf (Crash): Bug 1184328

This might be interesting here, because...
 * The crash SIGSEGV in GlobalParams::findFontFile() could have the same reason like the problem in evince, but evince seems to handle it better.
 * xpdf uses libpoppler19 0.18.4-1ubuntu3.1, but not libcairo.
 * evince uses
   - libpoppler-glib8 0.18.4-1ubuntu3
   - libpoppler19 0.18.4-1ubuntu3
   - libcairo-gobject2 1.10.2-6.1ubuntu3
   - libcairo2 1.10.2-6.1ubuntu3

Maybe this is libpoppler19 0.18.4-1ubuntu3.1 related.

summary: Evince does not display some fonts: "Error: could not create type1 face
- some font thing failed"
+ some font thing failed" - okular, epdfview and zathura also affected by
+ this issue.
Revision history for this message
Michael Mess (michael-michaelmess) wrote :

Could be also related to fontconfig-config 2.8.0-3ubuntu9.1 and libfontconfig1 2.8.0-3ubuntu9.1 which is not used by mupdf which has no issues displaying the document, but used by xpdf (Bug 1184328) and evince, epdfview, okular and zathura (this bug).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in epdfview (Ubuntu):
status: New → Confirmed
Changed in fontconfig (Ubuntu):
status: New → Confirmed
Changed in okular (Ubuntu):
status: New → Confirmed
Changed in poppler (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Mess (michael-michaelmess) wrote :
Revision history for this message
Michael Mess (michael-michaelmess) wrote :

After upgrade to Ubuntu 14.04 LTS:

Testing the file DOSB_Pruefungswegweiser_Komplett_web_11_12.pdf with various pdf viewers again after upgrading to Ubuntu 14.04 LTS.

 * evince: OK
 * okular: OK
 * epdfview: OK
 * xpdf: OK
 * zathura: OK

Thus this bug seem to be fixed with Ubuntu 14.04 LTS.

Changed in poppler (Ubuntu):
status: Confirmed → Fix Released
Changed in fontconfig (Ubuntu):
status: Confirmed → Invalid
Changed in evince (Ubuntu):
status: Confirmed → Fix Released
Changed in okular (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.