Ubuntu
poppler package

"Couldn't create a font" when opening a Korean PDF

Bug #47039 reported by atie
12
Affects Status Importance Assigned to Milestone
Poppler
Won't Fix
Medium
poppler (Ubuntu)
Won't Fix
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evince

Due to font errors, the PDFs at http://help.ubuntu.com/6.06/index.ko.html can't be readable by evince, only index of contents shown. But, using acroread they are readable as attached.

Font error were
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '1Eafd3UnBatang'

Revision history for this message
atie (atie-at-matrix) wrote : DesktopGuide.pdf readable by acroread

it's readable by acroread, I am using scim so I opened it with
GTK_IM_MODULE=xim acroread desktopguide.pdf

Revision history for this message
John Leach (johnleach) wrote : Re: Can't read the PDFs written in Korean at help.ubuntu.com

I get the same here on latest Dapper. 100% cpu too whilst it tries to render.

The Index list text in the sidebar seems to be displaying ok.

john@seiza:~$ evince Desktop/desktopguide.pdf
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
---snip---

Changed in evince:
status: Unconfirmed → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The example page has moved apparently, do still have the example? Could you point an another URI to download it or attach it to the bug?

Revision history for this message
John Leach (johnleach) wrote :

I've found a mirror of it which I'm attaching. It doesn't work in edgy either btw. Blank pages, high CPU.

Though, whilst searching for this mirror, I found a post by Matthew East regarding this problem. He claims to have found a workaround for it:

https://lists.ubuntu.com/archives/loco-contacts/2006-May/000303.html

Revision history for this message
Matthew East (mdke) wrote :

No, that post by me is not a workaround. The problem you see is due to a bug in the evince rendering engine that I reported in their bug tracker.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you have the number for the upstream bug you opened?

Revision history for this message
In , Sebastien Bacher (seb128) wrote :

That bug has been described on
https://launchpad.net/distros/ubuntu/+source/evince/+bug/47039:

"Due to font errors, the PDFs at http://help.ubuntu.com/6.06/index.ko.html can't
be readable by evince, only index of contents shown. But, using acroread they
are readable as attached.

Font error were
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '1Eafd3UnBatang'

http://librarian.launchpad.net/2953540/DesktopGuidePDF.png
it's readable by acroread, I am using scim so I opened it with
GTK_IM_MODULE=xim acroread desktopguide.pdf
...

I get the same here on latest Dapper. 100% cpu too whilst it tries to render.

The Index list text in the sidebar seems to be displaying ok.

john@seiza:~$ evince Desktop/desktopguide.pdf
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '2Eb071UnBatang,Bold'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
Error: Couldn't create a font for '1Eafd3UnBatang'
---snip---
...
> The example page has moved apparently, do still have the example? Could you
 point an another URI to download it or attach it to the bug?
...
http://librarian.launchpad.net/4442614/desktopguide.pdf
I've found a mirror of it which I'm attaching. It doesn't work in edgy either
btw. Blank pages, high CPU.
..."

The same issue happens with poppler 0.5.4 and poppler-data installed

Revision history for this message
In , Sebastien Bacher (seb128) wrote :

might be the same issue than bug #7093 or bug #8070

Revision history for this message
In , Matthew East (mdke) wrote :

Note that this bug isn't just with Korean fonts, it applies to any PDF I've
tried with embedded truetype fonts. I'll attach an English one.

Revision history for this message
In , Matthew East (mdke) wrote :

Created an attachment (id=7225)
English PDF with embedded truetype fonts

As promised, here is the attachment.

Revision history for this message
Matthew East (mdke) wrote : Re: [Bug 47039] Re: Can't read the PDFs written in Korean at help.ubuntu.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Seb,

* Sebastien Bacher:
> do you have the number for the upstream bug you opened?

Yes, it's https://bugs.freedesktop.org/show_bug.cgi?id=6728
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFH4Y2tSaF0w5rBv8RAhicAKCBfs/9MMw/fP5WddyEkoySzrP9bACfXflc
Msg8D0tWu2BHdJzYQmuqTeU=
=qGjC
-----END PGP SIGNATURE-----

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: Can't read the PDFs written in Korean at help.ubuntu.com

Matthew, the bug you point is a crasher, seems to be a different issue

Revision history for this message
Matthew East (mdke) wrote : Re: [Bug 47039] Re: Can't read the PDFs written in Korean at help.ubuntu.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Sebastien Bacher:
> Matthew, the bug you point is a crasher, seems to be a different issue

It also says: "The rendering is broken too". That bug is the one that
was opened when I presented the issue to the #evince channel on irc.

Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFH7tutSaF0w5rBv8RAiiiAJ9dZ4pzO+lcWUV++DA7M+RLe+zRzgCfY2PH
ig2KrGyeX3JtubCovLXrRuY=
=rD6J
-----END PGP SIGNATURE-----

Revision history for this message
Sebastien Bacher (seb128) wrote :

I've forwarded that upstream: https://bugs.freedesktop.org/show_bug.cgi?id=8472

Changed in evince:
assignee: nobody → desktop-bugs
Bug Watch Updater (bug-watch-updater)
Changed in poppler:
status: Unknown → Confirmed
Revision history for this message
In , Sebastien Bacher (seb128) wrote :

Created an attachment (id=7633)
another example

Revision history for this message
In , John Leach (johnleach) wrote :

this is still a problem on Ubuntu feisty, which sports libpoppler 0.5.4.

Any news?

Revision history for this message
In , Brad Hards (bradh) wrote :

Some font fixes just went into poppler head.

If possible, can you test again with that configuration? Even confirming if it is still a problem with poppler 0.6.2 would be useful.

Revision history for this message
In , Sebastien Bacher (seb128) wrote :

Using libpoppler 0.6.2
- the description example doesn't open in evince, it's using over 1.6G in tmp and breaking due to the lack of space there
- the desktopguide.pdf example is still displayed empty and "some font thing failed" lines are written on the command line
- using test-poppler-glib displays identic "some font thing failed" warnings

Revision history for this message
In , Brad Hards (bradh) wrote :

I finally got around to trying this with Qt4 tools on top-of-tree. Still bad.

Revision history for this message
In , Albert Astals Cid (aacid) wrote :

"Couldn't create a font for" errors are due to FreeType erroring on loading some font, i reported the problem to them and they said the fonts are broken and will not support them.

Sorry there's nothing more i can do.

Bug Watch Updater (bug-watch-updater)
Changed in poppler:
status: Confirmed → Won't Fix
Revision history for this message
Pedro Villavicencio (pedro) wrote :

won't fix at the upstream bug tracker:

"
"Couldn't create a font for" errors are due to FreeType erroring on loading
some font, i reported the problem to them and they said the fonts are broken
and will not support them.

Sorry there's nothing more i can do.
"

Changed in poppler:
status: Confirmed → Won't Fix
Bug Watch Updater (bug-watch-updater)
Changed in poppler:
importance: Unknown → Medium
Bug Watch Updater (bug-watch-updater)
Changed in poppler:
importance: Medium → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in poppler:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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