Printing certain documents yields characters scattered all over the page

Bug #661724 reported by Peter M. Clausen
236
This bug affects 37 people
Affects Status Importance Assigned to Milestone
Evince
Unknown
Critical
cairo
Fix Released
High
cairo (Ubuntu)
Fix Released
Low
Unassigned
Maverick
Fix Released
Low
Unassigned

Bug Description

Binary package hint: evince

Print of document produces scattered characters all over document, figures are OK

Display is OK. It seems similar to bug #457574 but I added a new one, since its "fixed" for Hardy.

Whats more strange is that print to PDF and PS produces a correct document.

To reproduce:
- Load attached pdf in evince
- Print preview (print preview as well as print is corrupt)

Workaround:
- Print to pdf
- Open new pdf and print is (correct print preview as well as print)

I dont know if its important - my printer is a network printer over Wlan, HP deskjet 930C, with standard driver from ubuntu. It prints without problems (corrupt documents, as well as the correct pdf after printing to pdf)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evince 2.32.0-0ubuntu1
ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature'
Uname: Linux 2.6.35-02063507-generic i686
Architecture: i386
Date: Sat Oct 16 14:58:00 2010
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: evince

== Regression details ==
Discovered in version: 1.10.0-1ubuntu2
Last known good version: 1.8.10-2ubuntu1

Revision history for this message
Peter M. Clausen (pclausen) wrote :
Revision history for this message
Peter M. Clausen (pclausen) wrote :

Corrupt print in preview

Revision history for this message
RHIFT (brad-rhift) wrote :

Ubuntu 10.10
Evince 2.32.0
poppler/cairo (0.14.3)

I am experiencing the exact same bug when printing my electric bill PDF from evince. Seemingly random/strange characters are printed all over the document when printing from Evince it, but it renders correctly when viewing in Evince.

Even if I use "Print to file" I get the exact same result (see attached printing of Peter's PDF since I don't want my electric bill on the Internet [evince-print-to-file.pdf]). After printing to file, if I open the printed-to-file file, and then print it to file again, it adds more random characters.

I can print correctly from XPDF and Okular.

Revision history for this message
RHIFT (brad-rhift) wrote :
Revision history for this message
wesnick (spanishwes) wrote :

I am also experiencing this bug, using the pdf file from FinCEN:
http://www.fincen.gov/fin104_ctr.pdf

Characters are scattered over the document both printing to printer and to file from evince.

AMD x86_64
2.6.35-22-generic

Attached output.

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=629403

summary: - Print of document scattered characters over document, figures OK
+ Printing certain documents yields characters scattered all over the page
Changed in evince (Ubuntu):
status: New → Confirmed
Changed in evince:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
tchize (tchize-gmail) wrote :
Revision history for this message
Toki (thonaldo) wrote :

I am also affected by this bug.
But contrary to the first posting, "print to file" has the same problem, and even the print preview contains the scattered letters.
The result from my experiments with the aforementioned spring-reference.pdf were:

- printing directly from evince has scattered letters
- printing to pdf has scattered letters
- selecting "print to file" with the pdf option yields scattered letters (in the print preview and the file)

- printing via command line "lpr spring-reference.pdf" works!
- printing to ps works
- selecting "print to file" with the ps option works (in the print preview and the file)
- other viewers (such as xpdf) work, because they simply use the "lpr" command

It also doesn't work with my personal pdf files, which were created by pdflatex. So they probably don't contain obscure propietary pdf extensions...

Thus I suspect a bug in the pdf processing of the gnome or evince printing framework.

Revision history for this message
Damian Nadales (dnadales) wrote :

As Toki pointed out, now my own documents, which I produce using pdflatex as well, have the same problem. If I print using the vieewer epdfview I have no problem.

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

This turned out to be a bug not in evince but in the cairo library (that evince uses for printing). I submitted it upstream and it got fixed immediately: https://bugs.freedesktop.org/show_bug.cgi?id=31062
Now the only task remaining is to get this fix into Ubuntu.

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

Changing the affected package to cairo.

affects: evince (Ubuntu) → cairo (Ubuntu)
Changed in evince:
status: New → Unknown
Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

The linked branch contains the backported upstream fix -- testing welcome!

description: updated
tags: added: regression-release
Revision history for this message
Toki (thonaldo) wrote :

Thanks Marcel!
I just tried your branch and all of the issues are gone. Printing to the printer works and so does printing to a file :)

Revision history for this message
Ruben Verhack (ruben-verhack) wrote :

Hey,

How long will it take for this patch to arrive in the maverick updates? Or can you explain to me what I have to do with the .patch files?

I updated to Maverick, because I though this would fix my printing issues.

Thanks!

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

Thank you for your work on that, the patch should land in natty and maverick-proposed in the next days

Changed in cairo (Ubuntu):
importance: Undecided → Low
status: Confirmed → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

uploaded now, somebody from ubuntu-sru needs to approve the upload next

Changed in cairo (Ubuntu Maverick):
importance: Undecided → Low
status: New → Fix Committed
Revision history for this message
loafing (guojq28) wrote :

would somebody told me how to do the patch myself?
wanted to keep up with the new version of ubuntu. I ended up getting a huge bug.

Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted cairo into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Donjan Rodic (bryonak) wrote :

Confirming fix on Ubuntu 10.10 amd64. No more scrambled output.
Thanks!

tags: added: verification-done
removed: verification-needed
Revision history for this message
Damian Nadales (dnadales) wrote :

I can also confirm the fix. I do not get scattered characters anymore. Thank you.

Revision history for this message
Ondergetekende (kvdveer) wrote :

Works for me too...
Thanks for the effort people!

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

This bug was fixed in the package cairo - 1.10.0-1ubuntu3

---------------
cairo (1.10.0-1ubuntu3) maverick-proposed; urgency=low

  * debian/patches/05_fix_glyph_advance.patch
    Backport upstream fix for broken print output in evince. (LP: #661724)
 -- Marcel Stimberg <email address hidden> Mon, 25 Oct 2010 00:56:57 +0200

Changed in cairo (Ubuntu Maverick):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Copied to natty, too

Changed in cairo (Ubuntu):
status: Fix Committed → Fix Released
Changed in cairo:
status: Unknown → Fix Released
Changed in cairo:
importance: Unknown → High
Revision history for this message
Luis Carlos Cobo (luiscarlos) wrote :

I am experiencing this issue with an up-to-date 11.10 Ubuntu system.

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

@luiscarlos: Are you sure you have the updates repository enabled? Could you run
apt-cache policy libcairo2
in a terminal and paste the ouput? Thanks.

Revision history for this message
Jan Middelkoop (jan-recreatie-zorg) wrote :

I am experiencing this issue with Natty.

> # apt-cache policy libcairo2
> libcairo2:
> Installed: 1.10.2-2ubuntu2
> Candidate: 1.10.2-2ubuntu2
> Version table:
> *** 1.10.2-2ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
> 100 /var/lib/dpkg/status

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

@luiscarlos and @jan-recreatie-zorg: all Ubuntu versions > 10.04 (maverick) have this specific issue fixed, I therefore think you are not seeing the same bug. In case you are seeing this problem even when printing to a file (like in this bug report), please report a new bug against libcairo2 (ideally using "ubuntu-bug libcairo2" in a terminal). It is helpful if you can attach an example file where you are experiencing this issue, together with the result of printing to a file. If you are only seeing the issue when printing to a real printer, report a bug against the CUPS package ("ubuntu-bug cups"). Ideally, follow the steps described here: https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data
Thanks in advance!

Revision history for this message
Jan Middelkoop (jan-recreatie-zorg) wrote :

@marcelstimberg You are correct, this does not appear in print previews or while printing to a file. I will file a new bug report per your guidelines. :-) Thank you.

Revision history for this message
Jan Middelkoop (jan-recreatie-zorg) wrote :

For anyone finding this bug report experiencing the same problem as me, have a look at this bug#277404. Specifically comment 35 in that bug:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/277404/comments/35

Changing LanguageLevel from 3 to 2 in the PPD file remedied this problem for me.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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