Bug 617088 – Document fine in Evince - broken in Adobe

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 617088 - Document fine in Evince - broken in Adobe


Summary:	Document fine in Evince - broken in Adobe


Status:	RESOLVED INCOMPLETE

Product:	gnome-print
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Jody Goldberg
QA Contact:	Jody Goldberg

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-04-28 15:33 UTC by Jim Ross
Modified:	2010-12-17 06:10 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
broken in Acrobat - fine elsewhere (48.03 KB, application/pdf) 2010-04-28 15:33 UTC, Jim Ross	Details

Description Jim Ross 2010-04-28 15:33:35 UTC

Created attachment 159802 [details]
broken in Acrobat - fine elsewhere

gnome-sudoku has a feature to print to pdf.  While using libgnomeprint version 2.18.6, the document it produced does not display properly in Acrobat Reader.  The document works fine in other readers though.

Please see Bug 613141 for the discussion of the problem on the game bug list.

As far as the game is concerned - this problem is fixed because it has been modified to use cairo for printing.  Basically it looks like a gnome-print bug, but I couldn't find any bugs that matched the description in the gnome-print bug list.

I'm attaching the example pdf.  When you look at it in Acrobat Reader the last sudokus on each full page are blank.  The same file looks fine in other readers.

Comment 1 André Klapper 2010-10-29 16:00:28 UTC

Which gnome-sudoku version is this about? I have huge doubts that libgnomeprint is involved here as printing was moved to GTK since version 2.14.

Comment 2 Fabio Durán Verdugo 2010-12-17 06:10:09 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!