some characters not displayed in a PDF file

Bug #1020162 reported by Laurent Bonnaud on 2012-07-02
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Poppler
Fix Released
Medium
poppler (Ubuntu)
High
Unassigned
Precise
High
Unassigned
Quantal
Low
Unassigned

Bug Description

Impact:
Some part of the text is not displayed in some pdf documents

Test Case:
open https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1020162/+attachment/3210969/+files/Bug.pdf in evince, see if the text is fully displayed

Regression potential:
Check that other pdfs still render fine

Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that's like a poppler issue, would be nice to forward upstream on bugs.freedesktop.org

affects: evince (Ubuntu) → poppler (Ubuntu)

I tested in Debian experimental and this bug is still there with those package versions:

Package: libpoppler26
Version: 0.20.1-1

Package: evince
Version: 3.4.0-2+b1

Since this is the latest upstream version, it makes sense to report it upstream. I will do it...

Created attachment 63754
File to reproduce the bug

The PDF file attached to this bug is not displayed correctly by evince and okular. In the terminal where evince was started many instances of this error message are displayed:

Error: failed to load truetype font

some font thing failed

gv is able to display this file correctly.

This bug is present in Ubuntu 12.04 and Debian experimental with the following package versions:

Package: libpoppler26
Version: 0.20.1-1

Package: evince
Version: 3.4.0-2+b1

Changed in poppler:
importance: Unknown → Medium
status: Unknown → Confirmed

This bug still exists in Ubuntu quantal with this package version:

Package: libpoppler28
Version: 0.20.4-0ubuntu1

Will be fixed in poppler 0.22

Changed in poppler:
status: Confirmed → Fix Released

Thank you for the fix! I am looking forward to the integration of this new version in Linux distributions...

Changed in poppler (Ubuntu):
importance: Undecided → High
status: New → Fix Committed
Sebastien Bacher (seb128) wrote :

There is already a SRU in the queue but we should probably include that one for the next stable update as well

Changed in poppler (Ubuntu Quantal):
status: New → Triaged
importance: Undecided → Low
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package poppler - 0.20.5-0ubuntu2

---------------
poppler (0.20.5-0ubuntu2) raring; urgency=low

  * debian/patches/git_mask_segfault.patch:
    - don't segfault in setSoftMaskFromImageMask (lp: #1034229)
  * debian/patches/git_no_buggy_check.patch:
    "Don't do a check for sanity that then we don't use" (lp: #1020162)
 -- Sebastien Bacher <email address hidden> Mon, 03 Dec 2012 18:47:40 +0100

Changed in poppler (Ubuntu):
status: Fix Committed → Fix Released
Changed in poppler (Ubuntu Precise):
status: New → Triaged
importance: Undecided → High
description: updated
Changed in poppler (Ubuntu Precise):
status: Triaged → In Progress
Changed in poppler (Ubuntu Quantal):
status: Triaged → In Progress

Hello Laurent, or anyone else affected,

Accepted poppler into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/poppler/0.18.4-1ubuntu3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in poppler (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Simon Déziel (sdeziel) wrote :

The fix works well.

tags: added: verification-done
removed: verification-needed

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package poppler - 0.18.4-1ubuntu3

---------------
poppler (0.18.4-1ubuntu3) precise-proposed; urgency=low

  * debian/patches/git_no_buggy_check.patch:
    "Don't do a check for sanity that then we don't use" (lp: #1020162)
 -- Sebastien Bacher <email address hidden> Tue, 04 Dec 2012 19:39:07 +0100

Changed in poppler (Ubuntu Precise):
status: Fix Committed → Fix Released

I am using evince 3.6.0 on Ubuntu 12.10 and I am experiencing a similar problem. PDF check files with helvetica and courier fonts view correctly but when printed on brother or hp laser printers place the $ sign over the left most number character.
When printing the same file using Evince 3.4.0 on Lubuntu 12.04 it prints correctly.

For the record, this bug is now fixed in Ubuntu raring with this package version:

Package: libpoppler28
Version: 0.20.5-1ubuntu3

Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in poppler (Ubuntu Quantal):
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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