bug: 150187 title: Evince has very bad quality when printing pdf files. date-reported: Sun, 07 Oct 2007 13:23:46 -0000 date-updated: Sun, 23 Nov 2014 15:09:40 -0000 reporter: Vincenzo Ciancia (vincenzo-ml) duplicate-of: duplicates: 141325 154763 156261 285666 attachments: https://bugs.launchpad.net/bugs/150187/+attachment/158155/+files/evince-print.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/158156/+files/kpdf-print.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/177538/+files/output.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/177539/+files/prezentace.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/177780/+files/one_page.ps application/postscript https://bugs.launchpad.net/bugs/150187/+attachment/177781/+files/two_pages.ps application/postscript https://bugs.launchpad.net/bugs/150187/+attachment/177816/+files/Capture.png image/png https://bugs.launchpad.net/bugs/150187/+attachment/179285/+files/Primer%20examen%20DAE.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/182578/+files/test-lyx-math.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/205035/+files/photo.jpg image/jpeg https://bugs.launchpad.net/bugs/150187/+attachment/205046/+files/grab.jpg image/jpeg https://bugs.launchpad.net/bugs/150187/+attachment/270329/+files/speciation_state_correlation.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/287978/+files/libpoppler2_0.6.4-1ubuntu1_i386.deb application/x-debian-package https://bugs.launchpad.net/bugs/150187/+attachment/287979/+files/libpoppler-glib2_0.6.4-1ubuntu1_i386.deb application/x-debian-package https://bugs.launchpad.net/bugs/150187/+attachment/287984/+files/poppler.diff text/plain https://bugs.launchpad.net/bugs/150187/+attachment/290756/+files/Haut_A4.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/617422/+files/groups.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/617423/+files/a.pdf application/pdf https://bugs.launchpad.net/bugs/150187/+attachment/617424/+files/b.pdf application/pdf patches: tags: gutsy hardy intrepid regression subscribers: Thom Pischke (thom-pischke) David Vonka (vonkad) Ricardo Pérez López (ricardo) b (ben-ekran) Håvard H. Garnes (hhgarnes) Swistak (swistakers) xtknight (xt-knight) Hanno Stock (hefe_bia) (hanno-stock) Mark Jovalekic (m-jovalekic) wolf87 (ablocker) Neilen Marais (neilenmarais) Pelládi Gábor (pelladigabor) Felipe Figueiredo (philsf) jarondl (jarondl) Marcin Kowalczyk (qrczakmk) David Tombs (dgtombs) Niels Egberts (nielsegberts) Litrik De Roy (litrik) Christian Schlauer (cs-usenet) task: poppler status: Fix Released date-created: Wed, 10 Oct 2007 10:52:27 -0000 date-triaged: Sun, 02 Nov 2008 07:52:58 -0000 date-inprogress: Sun, 02 Nov 2008 07:52:58 -0000 date-closed: Sun, 02 Nov 2008 07:52:58 -0000 date-fix-committed: Sun, 02 Nov 2008 07:52:58 -0000 date-fix-released: Sun, 02 Nov 2008 07:52:58 -0000 reporter: Sebastien Bacher (seb128) watch: https://bugs.freedesktop.org/show_bug.cgi?id=12769 importance: Medium assignee: milestone: task: cupsys (Ubuntu) status: Invalid date-created: Sun, 07 Oct 2007 13:23:46 -0000 date-closed: Sun, 07 Oct 2007 13:44:42 -0000 reporter: Vincenzo Ciancia (vincenzo-ml) importance: Undecided component: main assignee: milestone: task: poppler (Ubuntu) status: Fix Released date-created: Sun, 07 Oct 2007 13:41:42 -0000 date-confirmed: Mon, 20 Jul 2009 16:25:33 -0000 date-triaged: Mon, 20 Jul 2009 16:25:33 -0000 date-assigned: Thu, 08 May 2008 13:24:56 -0000 date-inprogress: Mon, 20 Jul 2009 16:25:33 -0000 date-closed: Mon, 20 Jul 2009 16:25:33 -0000 date-fix-committed: Mon, 20 Jul 2009 16:25:33 -0000 date-fix-released: Mon, 20 Jul 2009 16:25:33 -0000 date-left-closed: Tue, 30 Jun 2009 11:54:26 -0000 reporter: Vincenzo Ciancia (vincenzo-ml) importance: Medium component: main assignee: Sebastien Bacher (seb128) milestone: task: cupsys (Ubuntu Hardy) status: Invalid date-created: Thu, 05 Jun 2008 19:59:53 -0000 date-left-new: Thu, 05 Jun 2008 20:36:58 -0000 date-closed: Thu, 05 Jun 2008 20:36:58 -0000 reporter: Steve Langasek (vorlon) importance: Undecided assignee: milestone: task: poppler (Ubuntu Hardy) status: Won't Fix date-created: Thu, 05 Jun 2008 19:59:53 -0000 date-left-new: Thu, 05 Jun 2008 20:00:28 -0000 date-closed: Sun, 23 Nov 2014 15:09:39 -0000 reporter: Steve Langasek (vorlon) importance: Low assignee: milestone: Content-Type: multipart/mixed; boundary="===============7638371431175314561==" MIME-Version: 1.0 --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Evince prints every pdf I send, with very bad quality, and printing is very slow. Kpdf does not suffer of this problem, printing is high quality and fast. Looks like evince is rendering pdf to a very low quality image. I also tried printing some text from gedit, and it is of perfect quality too. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Sun, 07 Oct 2007 13:44:41 -0000 Message-Id: <20071007134442.908.20120.malone@potassium.ubuntu.com> After discovering that I had the same problem with another printer, I tried with kpdf, and printing is perfect. Evince has very bad quality when printing pdfs. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Till Kamppeter (till-kamppeter) Date: Sun, 07 Oct 2007 14:20:21 -0000 Message-Id: <20071007142021.908.27035.malone@potassium.ubuntu.com> One hint about the Ricoh problem which you described in your original bug report. Due to space reasons we could not put all manufacturer- supplied PostScript printer PPDs onto the desktop CDs. To get the full set including all Ricoh PPDs, install the openprinting-ppds-extra package. This will naturally not have any influence of the output quality of evince, but it gives you access to the full functionality of your printer. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Sun, 07 Oct 2007 15:28:24 -0000 Message-Id: <20071007152824.11903.22807.malone@gandwana.ubuntu.com> Thanks a lot. This should be suggested at some stage after installation. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Sun, 07 Oct 2007 20:35:50 -0000 Message-Id: <20071007203550.11903.45589.malone@gandwana.ubuntu.com> There is no other bug about that, maybe that's a configuration issue --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Sun, 07 Oct 2007 22:25:21 -0000 Message-Id: <20071007222521.16607.73466.malone@gangotri.ubuntu.com> Just today I was talking to a collegue who had the same problem on gutsy beta. He used acroread and he went fine. However, I tried to print via cups-pdf and the produced pdf is just fine. Sebastien, do you have any advice on how to produce more information? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Sun, 07 Oct 2007 22:30:37 -0000 Message-Id: <20071007223038.11903.90409.malone@gandwana.ubuntu.com> It seems that I spoke too early. I printed again one page via cups-pdf, both from evince and from kpdf. I attach the results of both. The one printed via evince occupies much more disk space, and if you zoom onto that you'll notice these are bitmaps. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Sun, 07 Oct 2007 22:31:05 -0000 Message-Id: <20071007223105.11903.74999.malone@gandwana.ubuntu.com> --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Sun, 07 Oct 2007 22:31:37 -0000 Message-Id: <20071007223137.16607.11583.malone@gangotri.ubuntu.com> --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Wed, 10 Oct 2007 03:51:33 -0000 Message-Id: <20100914164609.4895.60891.launchpad@loganberry.canonical.com> The bug has been opened on https://bugs.launchpad.net/bugs/150187 "Evince prints every pdf I send, with very bad quality, and printing is ver= y slow. Kpdf does not suffer of this problem, printing is high quality and = fast. Looks like evince is rendering pdf to a very low quality image. I als= o tried printing some text from gedit, and it is of perfect quality too. ... After discovering that I had the same problem with another printer, I tried= with kpdf, and printing is perfect. Evince has very bad quality when print= ing pdfs. ... It seems that I spoke too early. I printed again one page via cups-pdf, bot= h from evince and from kpdf. I attach the results of both. The one printed = via evince occupies much more disk space, and if you zoom onto that you'll = notice these are bitmaps. ... http://launchpadlibrarian.net/9860625/evince-print.pdf ... http://launchpadlibrarian.net/9860627/kpdf-print.pdf ..." --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Carlos Garcia Campos (carlosgc) Date: Wed, 10 Oct 2007 03:55:06 -0000 Message-Id: <20100914164618.4895.67064.launchpad@loganberry.canonical.com> In evince we are directly rendering into a ps/pdf cairo surface with poppler_page_render(). I'm not sure whether it's a poppler or cairo issue. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Wed, 10 Oct 2007 10:52:12 -0000 Message-Id: <20071010105212.19156.44954.malone@gangotri.ubuntu.com> Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: https://bugs.freedesktop.org/show_bug.cgi?id=3D12769 --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Jeff Muizelaar (jeff-infidigm) Date: Fri, 12 Oct 2007 22:02:41 -0000 Message-Id: <20100914164618.4895.16379.launchpad@loganberry.canonical.com> I don't think this is a poppler bug... My guess is that we are hitting the image fallback of the pdf surface. I'd = expect that images produced should be higher resolution. i.e. Someone shoul= d be calling cairo_surface_set_fallback_resolution. Though, I'm not sure wh= o should be doing this. I'd expect the gtk printing infrastructure to do it= , but I could be wrong. It looks like there is also a problem with how image masks are scaled. We do the scaling ourselves in poppler and I believe that will cause unnecessarily low resolution results. Also of note, cairo-git does fine grained fallbacks and so the problem is not as noticeable. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Carlos Garcia Campos (carlosgc) Date: Sat, 13 Oct 2007 10:29:45 -0000 Message-Id: <20100914164618.4895.90422.launchpad@loganberry.canonical.com> (In reply to comment #2) > I don't think this is a poppler bug... > My guess is that we are hitting the image fallback of the pdf surface. I'd > expect that images produced should be higher resolution. i.e. Someone sho= uld be > calling cairo_surface_set_fallback_resolution.=20 The first thing I tried was calling cairo_surface_set_fallback_resolution in evince and calling displaySlice with 300 instead of 72 in poppler-glib, but it didn't help. > Though, I'm not sure who should > be doing this. I'd expect the gtk printing infrastructure to do it, but I= could > be wrong. In evince we are only using the gtk+ printing dialog, but not gtkprintoperation, so it should be done in evince. > It looks like there is also a problem with how image masks are scaled. We= do > the scaling ourselves in poppler and I believe that will cause unnecessar= ily > low resolution results. >=20 > Also of note, cairo-git does fine grained fallbacks and so the problem is= not > as noticeable. >=20 It seems there are many changes in cairo git that fix things in poppler/evince. Do you know if there are plans to release cairo soon? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?L=C3=A9o_Studer_=28leo-studer=29?= Date: Tue, 20 Nov 2007 00:30:04 -0000 Message-Id: <20100914164618.4895.51752.launchpad@loganberry.canonical.com> (In reply to comment #3) I still have this bug. Are there any plan to fix it in the close future ? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Tue, 27 Nov 2007 09:04:26 -0000 Message-Id: <20100914164618.4895.21876.launchpad@loganberry.canonical.com> Additionally, why does printing a PDF to a PDF surface invoke a raster- image fallback? I could see why, sometimes, printing a PDF to PS would invoke a raster-image fallback. However, normally, printing to PS should only create an image for the parts of the document that cannot be handled using vector graphics. Can someone clarify what is going on? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Tue, 27 Nov 2007 15:53:10 -0000 Message-Id: <20071127155310.1446.26609.malone@potassium.ubuntu.com> Also confirmed here, Gutsy amd64, evince 2.20.1. The bad printing quality can already be seen in the printing preview... --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Tue, 04 Dec 2007 09:30:49 -0000 Message-Id: <20071204093049.28264.23749.malone@gandwana.ubuntu.com> For me, this bug seems to be fixed since the newest updates (till 12-04) fo= r my Gutsy amd64 (evince 2.20.1-0ubuntu1, libcairo2 1.4.10-1ubuntu4.1), pri= nting quality is now normal again. Can anyone confim this? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?L=C3=A9o_Studer_=28leo-studer=29?= Date: Tue, 04 Dec 2007 09:50:14 -0000 Message-Id: <20071204095014.23271.39903.malone@gangotri.ubuntu.com> The libcairo2 update did not fixed the problem with me, evince's printing quality is still outstandingly bad for some documents --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: David Vonka (vonkad) Date: Tue, 04 Dec 2007 13:54:16 -0000 Message-Id: <20071204135416.28314.12444.malone@gandwana.ubuntu.com> Well, I have certainly noted some improvement. Documents that were completely messed up before now print reasonably and documents, where half of some pages didn't print at all (a different bug) now print correctly. However, not everything is quite all right. I attach a pdf- latex beamer presentation of mine. Everything prints ok, but the nonalphanumeric signs, like < (on slide 6), and different arrows (slide 7 and 9) and stars on slide 11. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: David Vonka (vonkad) Date: Tue, 04 Dec 2007 13:55:15 -0000 Message-Id: <20071204135515.23362.51372.malone@gangotri.ubuntu.com> --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Andrey Vihrov (andrey.vihrov) Date: Tue, 04 Dec 2007 14:06:45 -0000 Message-Id: <20071204140645.23362.20841.malone@gangotri.ubuntu.com> The 4th December libcairo2 updates do not fix the issue. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Wed, 05 Dec 2007 03:51:22 -0000 Message-Id: <20100914164618.4895.54744.launchpad@loganberry.canonical.com> If that helps: Printing two pages on one page of paper results in good quality, while printing one page on one page does not. Using evince 2.20.1-0ubuntu1, libcairo2 1.4.10-1ubuntu4.1. See launchpad bug for attachments. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Wed, 05 Dec 2007 11:38:52 -0000 Message-Id: <20071205113852.30928.24118.malone@potassium.ubuntu.com> Ah, okay. I agree, that it doesn't fix the bug. I printed two pages on one, which results in good quality. Printing one page still gives bad quality output. Also I notice, that formulas are printed correctly, while normal text is not. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Wed, 05 Dec 2007 11:39:43 -0000 Message-Id: <20071205113943.28264.3658.malone@gandwana.ubuntu.com> --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?L=C3=A9o_Studer_=28leo-studer=29?= Date: Wed, 05 Dec 2007 13:17:36 -0000 Message-Id: <20071205131736.28314.31108.malone@gandwana.ubuntu.com> I agree with der_vegi: text is blurry while mathematic formulas are more clear. (see attached screenshot) --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Andrey Vihrov (andrey.vihrov) Date: Wed, 05 Dec 2007 19:47:08 -0000 Message-Id: <20071205194708.23271.68396.malone@gangotri.ubuntu.com> Maybe the quality depends on specific fonts. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?Ricardo_P=C3=A9rez_L=C3=B3pez_=28ricardo=29?= Date: Mon, 10 Dec 2007 11:22:07 -0000 Message-Id: <20071210112207.23709.77373.malone@gangotri.ubuntu.com> I have the same problem, too. Try generating a PDF using LyX, for example. I attach a file to illustrate the problem. This PDF file was generated using LyX. Try printing or previewing it: the result is very ugly. Printing the PDF file using Adobe Reader works perfectly. However, if you generate a .dvi file from the same LyX source, the printing result is perfect. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?b?VsOhY2xhdiDFoG1pbGF1ZXIgKGV1ZG94b3Mp?= Date: Tue, 11 Dec 2007 10:56:58 -0000 Message-Id: <20071211105659.23618.85359.malone@gangotri.ubuntu.com> I also confirm this, with both gutsy and current hardy, although the difference in quality here is much bigger that the PDFs from Vincenzo show. This is mostly with PDFs generated by pdftex using concrete fonts. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Tue, 11 Dec 2007 15:59:12 -0000 Message-Id: <20071211155912.23709.95949.malone@gangotri.ubuntu.com> Can anyone else confirm that printing two pages on one page results in normal quality? Also I noticed in my attachments above, that the resulting ps for two pages is about a third of the ps for one page... --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?L=C3=A9o_Studer_=28leo-studer=29?= Date: Wed, 12 Dec 2007 08:00:11 -0000 Message-Id: <20071212080011.12269.85869.malone@potassium.ubuntu.com> Printing two pages on one does indeed results in normal quality here. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?Ricardo_P=C3=A9rez_L=C3=B3pez_=28ricardo=29?= Date: Wed, 12 Dec 2007 11:06:39 -0000 Message-Id: <20071212110639.12269.62432.malone@potassium.ubuntu.com> Printing two pages on one with normal quality here, too. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Sun, 16 Dec 2007 05:58:56 -0000 Message-Id: <20100914164618.4895.23610.launchpad@loganberry.canonical.com> Installing old evince 0.8.1, libpoppler1 and libpoppler1-glib from the Feisty repos, leaving cairo unchanged, results in good quality again. So I don't think it is a cairo problem. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Carlos Garcia Campos (carlosgc) Date: Sun, 16 Dec 2007 07:32:28 -0000 Message-Id: <20100914164618.4895.29994.launchpad@loganberry.canonical.com> (In reply to comment #7) > Installing old evince 0.8.1, libpoppler1 and libpoppler1-glib from the Fe= isty > repos, leaving cairo unchanged, results in good quality again. So I don't= think > it is a cairo problem. >=20 In ev 0.8.x we didn't use cairo for printing. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Sun, 16 Dec 2007 12:26:06 -0000 Message-Id: <20071216122606.29645.2215.malone@gandwana.ubuntu.com> Maybe it is not a bug of poppler but of cairo? On the freedesktop bug, someone writes "I don't think this is a poppler bug...". Also, I would propose high priority, because printing .pdf files is a very common task in everyday's use.? Just imagine, how much ink is wasted these days, just because people think, this is a matter of dirty printing heads... ;) --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Sun, 16 Dec 2007 13:54:58 -0000 Message-Id: <20071216135458.29645.11812.malone@gandwana.ubuntu.com> Okay, it is not a problem of cairo. I installed evince, libpoppler1 and libpoppler1-glib from Feisty, which results in good quality output. Sorry for the many posts. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Serge Gavrilov (serge-pdmi) Date: Tue, 18 Dec 2007 10:33:55 -0000 Message-Id: <20100914164618.4895.54895.launchpad@loganberry.canonical.com> Beginning from evince 2.20 I cannot print many PDF files using my HP Color Laserjet 2605 printer. It is indicated here: http://bugzilla.gnome.org/show_bug.cgi?id=3D486740 It seems that these two bugs are related to each other. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Wed, 19 Dec 2007 18:29:25 -0000 Message-Id: <20071219182925.2219.18008.malone@gangotri.ubuntu.com> Ops, again I was wrong. "In ev 0.8.x we didn't use cairo for printing." So it could still be an issue of cairo.? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Fri, 21 Dec 2007 08:50:46 -0000 Message-Id: <20100914164620.4895.59744.launchpad@loganberry.canonical.com> I was hoping that this issue would be fixed now when libcairo2 version 1.5.4 is used. This is a development version that has two major features: - when printing an image, don't change the WHOLE PAGE to an image surface! - handle more PS/PDF vector constructions without resorting to an image f= allback. However, this does not seem to fix the problem. In fact, now both print preview and print-to-ps can take such a long time (with 100% cpu usage) that it seems that evince has crashed/hung - but if you wait long enough it will finish. This seems to be partly because the resulting files are too large. For example, printing a 30-page PDF file that was 271k, results in a 85M postscript file. During the printing to PS, no dialog boxes are shown, and evince seems to be usable during this time as long as you don't go to a new page. Unfortunately, the resulting files look really wierd, in that (sometimes) equations are just missing, as well as text being blurry. I have attached a very small pdflatex PDF that illustrates another kind of problem. When printing to PS, you see very blurry image fallbacks for normal text, and very clear equation text (you can zoom in). --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Fri, 21 Dec 2007 08:52:25 -0000 Message-Id: <20100914164620.4895.49326.launchpad@loganberry.canonical.com> Created an attachment (id=3D13290) Small math PDF that prints with blurry text When printing this PDF to PS, the equation text seems to remain as vector text, but the main text reverts to a very blurry image fallback. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Carlos Garcia Campos (carlosgc) Date: Fri, 21 Dec 2007 09:10:15 -0000 Message-Id: <20100914164620.4895.62232.launchpad@loganberry.canonical.com> Reassigning to cairo. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Fri, 21 Dec 2007 16:46:37 -0000 Message-Id: <20071221164637.27323.67284.malone@gangotri.ubuntu.com> I was hoping that this issue would be fixed now that libcairo2 version 1.5.4 has been uploaded. This is a development version that has two major features: - when printing an image, don't change the WHOLE PAGE to an image surface! - handle more PS/PDF vector constructions without resorting to an image f= allback. However, this does not seem to be the case. In fact, now both print preview and print-to-ps can take such a long time (with 100% cpu usage) that it seems that evince has crashed/hung - but if you wait long enough it will finish. This seems to be partly because the resulting files are too large. For example, printing a 30-page PDF file that was 271k, results in a 85M postscript file. During the printing to PS, no dialog boxes are shown, and evince seems to be usable as long as you don't go to a new page. Unfortunately, the resulting files look really wierd, in that (sometimes) equations are just missing, as well as text being blurry. I have attached a very small PDF that illustrates another kind of problem. When printing to PS, you see very blurry image fallbacks for normal text, and very clear equation text (you can zoom in). --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Thu, 03 Jan 2008 02:30:17 -0000 Message-Id: <20100914164620.4895.72989.launchpad@loganberry.canonical.com> In addition to the general "blurry printing" problem, it has been said that poppler has a problem print with image scaling when printing Type 3 fonts as bitmasks. This specific problem may be a poppler problem, rather than a cairo problem. So, I wanted to point out that there may be 2 problems here, and that the example PDF that I posted probably demonstrates the poppler problem, not the cairo problem. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Fri, 04 Jan 2008 08:39:07 -0000 Message-Id: <20100914164620.4895.61971.launchpad@loganberry.canonical.com> (In reply to comment #12) > Reassigning to cairo.=20 >=20 From the cairo list: "In the one_page.ps attached to the launchpad bug the Type 3 font is blurry while the Type 1 font is very sharp. So the use of fallpage image fallbacks by cairo is not the problem. The cause of the blurry text is most likely the image mask scaling done by poppler on Type 3 fonts." --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Sun, 20 Jan 2008 12:52:41 -0000 Message-Id: <20080120125241.2676.95599.malone@gandwana.ubuntu.com> So the cairo guys say, it is a problem of poppler, the poppler guys reassign it to cairo. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Wed, 06 Feb 2008 14:18:37 -0000 Message-Id: <20100914164620.4895.90556.launchpad@loganberry.canonical.com> That's still an issue --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?L=C3=A9o_Studer_=28leo-studer=29?= Date: Thu, 07 Feb 2008 08:36:13 -0000 Message-Id: <20080207083613.30658.68833.malone@potassium.ubuntu.com> I'm quite sorry this has not yet been sorted out, I still can't do serious printing with Gutsy computers here at the office, it's a serious stopper. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: b (ben-ekran) Date: Fri, 08 Feb 2008 19:15:00 -0000 Message-Id: <20080208191501.20809.34424.malone@gangotri.ubuntu.com> I can confirm this issue, with evince and my ml-2010. I'll attach some test images, but my quality issues seem even worse than the ones posted here. The type from my lyx document is almost unreadable. I decided to take a break from trying to read it to post here (I have a headache!). I don't print very often, so I'm pretty annoyed that now apparently I can't. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: b (ben-ekran) Date: Fri, 08 Feb 2008 19:19:35 -0000 Message-Id: <20080208191935.20947.92036.malone@gangotri.ubuntu.com> Notice for me the grey text is totally invisible in the photo, lighter than the text on the page underneath the one I'm photographing!! some words (italics) are unreadable because they are so blurry. Looking close to the output it looks like the text is dithered, no hard edges, no stark black, no edge. The printer is set to 600dpi, so I should be seeing crisp glyphs, not blurry half-tone. This is on gutsy with the gdi driver for ML-2010. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Mon, 25 Feb 2008 12:35:32 -0000 Message-Id: <20080225123532.5486.5363.malone@gangotri.canonical.com> I agree with gorgor, maybe the importance should be higher than "medium". --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?Ricardo_P=C3=A9rez_L=C3=B3pez_=28ricardo=29?= Date: Tue, 04 Mar 2008 09:42:30 -0000 Message-Id: <20080304094230.13048.49871.malone@gandwana.canonical.com> The problem is still present in latest Hardy. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Tue, 04 Mar 2008 12:14:28 -0000 Message-Id: <20080304121428.32095.36808.malone@gangotri.canonical.com> Problem is still there and we are about to release LTS, may I ask to developers reading this bug report what is the current situation and if plans are to release hardy with broken default pdf reader - for what a lot of people do with a pdf reader, i.e. print papers. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Tue, 04 Mar 2008 15:43:27 -0000 Message-Id: <20080304154327.8485.91142.malone@potassium.ubuntu.com> We could recommend acroread instead, since it actually works. Also, perhaps xpdf works in some cases when evince fails? If so, then we could recommend that. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?L=C3=A9o_Studer_=28leo-studer=29?= Date: Tue, 04 Mar 2008 15:54:29 -0000 Message-Id: <20080304155429.8485.72275.malone@potassium.ubuntu.com> I don't think getting around the issue is the solution. Evince is the offic= ial pdf viewing application for Gnome and should be able to work out of the= box. Also, acroread does not work straightforwardly for amd64. Plus it is a soft= ware one has to add manually, just like xpdf. So fact is Ubuntu would greatly benefit from this issue being fixed before = Hardy release, as I see now in the headers of the bug that it was declined = for Gutsy and transposed to Hardy. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Tue, 04 Mar 2008 16:07:15 -0000 Message-Id: <20080304160715.8485.28993.malone@potassium.ubuntu.com> gorgor: I completely agree. Why is this considered only "medium"? Perhaps because evince primarily fails to print SCIENTIFIC pdfs? (I am ask= ing if this is the case) For example, I think it has a lot of problems with PDFs created by TeX / Ly= X. But perhaps it works tolerably well with PDFs commonly found on the web= ? If so, perhaps the bugmasters consider this bug "medium" because they ar= en't scientists, and it works for them? Also, maybe this bug will just take a lot of investigation to solve, and that is the reason it is being listed as "medium" instead of "high" priority. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Fri, 07 Mar 2008 03:34:11 -0000 Message-Id: <20100914164620.4895.26335.launchpad@loganberry.canonical.com> Still present with evince 2.21.91-0ubuntu1, libpoppler2 0.6.4-1 and libcai= ro2 1.5.8-0ubuntu1. So do we know by now, if it is a problem of poppler (which the cairo-devs t= hink) or a problem of cairo? Does the fact, that printing two pages on one = results in good quality, give any clue? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adrian Johnson (ajohnson-redneon) Date: Fri, 07 Mar 2008 04:04:34 -0000 Message-Id: <20100914164620.4895.16192.launchpad@loganberry.canonical.com> (In reply to comment #16) > Still present with evince 2.21.91-0ubuntu1, libpoppler2 0.6.4-1 and libc= airo2 > 1.5.8-0ubuntu1. > So do we know by now, if it is a problem of poppler (which the cairo-devs > think) or a problem of cairo? Does the fact, that printing two pages on o= ne > results in good quality, give any clue? Re-assigning to poppler. This appears to be an image scaling problem in poppler. There was a patch committed to poppler which may fix the problem: http://lists.freedesktop.org/archives/poppler/2008-February/003459.html Currently waiting for confirmation that it fixes the problem: http://lists.freedesktop.org/archives/poppler/2008-February/003466.html I suggest testing with poppler 0.7.1 which contains this patch. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?H=C3=A5vard_H=2E_Garnes_=28hhgarnes=29?= Date: Fri, 07 Mar 2008 12:35:13 -0000 Message-Id: <20080307123514.9461.58276.malone@gangotri.canonical.com> I can confirm this bug as well --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Fri, 07 Mar 2008 16:15:37 -0000 Message-Id: <20080307161537.16116.11802.malone@gandwana.canonical.com> There seems to be a fix on its way upstream, see the remote freedesktop- bug. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Sun, 30 Mar 2008 09:15:26 -0000 Message-Id: <20100914164620.4895.42290.launchpad@loganberry.canonical.com> Well, I compiled poppler 0.7.3 (with cairo & glib) and still had the problem in evince, which told me it was using poppler 0.7.3 (cairo). But I should add, that I did a quick and dirty installation of poppler, which resulted in evince crashing on some documents... So I would not say that this test was too significant. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Swistak (swistakers) Date: Wed, 02 Apr 2008 21:53:57 -0000 Message-Id: <20080402215357.11557.92160.malone@gandwana.canonical.com> It's still present in hardy beta. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: xtknight (xt-knight) Date: Mon, 07 Apr 2008 03:08:32 -0000 Message-Id: <20080407030832.29800.18592.malone@gangotri.canonical.com> I didn't have much luck trying the fix for poppler on the freedesktop.org bug. First of all it's statically linked to evince so you have to recompile evince. You can't just test it by compiling poppler. Secondly, evince doesn't even compile with any other poppler (0.7.3, 0.8.0) than the distro version. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: xtknight (xt-knight) Date: Thu, 10 Apr 2008 15:05:58 -0000 Message-Id: <20100914164620.4895.86112.launchpad@loganberry.canonical.com> Poppler 0.7.1 contains this patch but does not solve the problem. Also confirmed evince was using 0.7.1 with About Dialog. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Serge Gavrilov (serge-pdmi) Date: Fri, 11 Apr 2008 02:22:37 -0000 Message-Id: <20100914164620.4895.46852.launchpad@loganberry.canonical.com> What version of cairo do you have installed? I have now cairo 1.5.20, poppler 0.6.3, and evince 2.22.0. I cannot reproduce the bug anymore. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: xtknight (xt-knight) Date: Fri, 11 Apr 2008 12:02:17 -0000 Message-Id: <20100914164620.4895.81626.launchpad@loganberry.canonical.com> I can reproduce with: libcairo2 1.6.0-0ubuntu1 (cairo 1.6.0) libpoppler2 0.6.4-1 (poppler 0.6.4) evince 2.22.1.1-0ubuntu1 (evince 2.22.1) It happens in the Print Preview even. The text is blurry but the equation looks sharp. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Mark Jovalekic (m-jovalekic) Date: Sat, 12 Apr 2008 08:06:48 -0000 Message-Id: <20080412080648.6085.85541.malone@gangotri.canonical.com> I must admit that I can't reproduce the bug, but I remember a similar probl= em I had years ago. It seems that the printing/display problems have something to do with docum= ents, which were created with some sort of TeX. You must know that font-handling (embedding) is often a cause for problems.= There are T1 (Type 1 =3D good, don't confuse it with T1 font encoding in y= our LaTeX source ;-) and T3 fonts. T3 are only the ugly bitmap fonts - I ha= ve seen (Alt + Enter in evince; than fonts dialog) that some of the PDFs ar= en't properly created. So please check your TeX/LaTeX/LyX-setup (I have installed texlive- fonts-recommended, -extra, -font-utils, and from universe the packages cm-super and lmodern) and your font settings in your sources / LyX- setup. Now the question is why do acroread, evince, kpdf show different output? Perhaps it is how they handle problems with fonts. I don't know, but it could be a possibility. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Sat, 12 Apr 2008 17:00:25 -0000 Message-Id: <20080412170025.10860.13958.malone@gandwana.canonical.com> Mark: Can you reproduce the problem with the attached PDF? For me, this 5-page PDF=20 (i) generates a blurry "Print Preview" (ii) takes 90 seconds to do so! Since the "Print Preview" does not match the displayed version of the PDF, = this definitely a bug in evince, not a natural result of using T3 fonts. =20 (Also, I used to have problems with bitmapped fonts, but I think that was actually a problem in dvips, and the problem was lack of anti- aliasing for on-screen presentations, not for printing; T3 fonts actually printed just fine.) --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Swistak (swistakers) Date: Sat, 12 Apr 2008 17:53:04 -0000 Message-Id: <20080412175304.10860.14186.malone@gandwana.canonical.com> I can reproduce it on hardy. When you attempt to use PDF printer the same happens - generates a blurry output in ~90 seconds. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Mark Jovalekic (m-jovalekic) Date: Sun, 13 Apr 2008 10:37:04 -0000 Message-Id: <20080413103704.11001.74449.malone@gandwana.canonical.com> @Benjamin Redelings: I can reproduce it on gutsy. I have noticed that your PDF includes T1 and T3 fonts. After printing into = a new PDF (or preview) the file becomes unusable - all fonts are gone (and = the filesize gets 1,2 MiB). Swistak gave me an idea: I create a "perfect" PDF with pdflatex with embedded T1 fonts. The file is shown in evince in good quality. When I print into a new PDF - the fonts are changed to T1C Cairo-fonts. The original ones are lost. The quality is still okay, but here we definitly see that there are some font handling problems. What do you think? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: wolf87 (ablocker) Date: Wed, 30 Apr 2008 01:55:09 -0000 Message-Id: <20080430015509.22266.95873.malone@gangotri.canonical.com> I found a fix. Mark was on the right track with the T1 & T3 fonts. I was having the exact same problem, and installing the package cm-super fixed it. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?L=C3=A9o_Studer_=28leo-studer=29?= Date: Wed, 30 Apr 2008 07:51:53 -0000 Message-Id: <20080430075153.32124.67941.malone@gandwana.canonical.com> Installing the cm-super package did not fix it for me --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Wed, 30 Apr 2008 10:27:44 -0000 Message-Id: <20080430102754.31543.47071.malone@gandwana.canonical.com> wolf87: perhaps you meant that it fixed for you in documents that you compile from latex? In any case, installing cm-super did NOT fix for me this bug, which is very bad quality from evince when printing certain pdf files. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Wed, 30 Apr 2008 11:28:23 -0000 Message-Id: <20080430112823.21851.88103.malone@gangotri.canonical.com> Patch provided here: http://lists.freedesktop.org/archives/poppler/2008-February/003459.html works. Please somebody report to upstream (I don't have a bugzilla account there). I succeded in backporting fix to poppler in hardy, but I had a problem: there is an additional argument in more recent versions of poppler: http://cgit.freedesktop.org/poppler/poppler/tree/glib/poppler-page.cc static void _poppler_page_render (PopplerPage *page, cairo_t *cairo, GBool printing) In ubuntu's version, "printing" is lacking. I used "true" instead of "printing" in my version of the patch and it works but developers should really take a look to what's going on. I attach two updated binary packages, diff will follow. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Wed, 30 Apr 2008 11:28:39 -0000 Message-Id: <20080430112839.31888.42751.malone@potassium.ubuntu.com> --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Wed, 30 Apr 2008 11:28:57 -0000 Message-Id: <20080430112857.21851.16247.malone@gangotri.canonical.com> --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Wed, 30 Apr 2008 11:33:15 -0000 Message-Id: <20080430113315.31888.42756.malone@potassium.ubuntu.com> My patch to current hardy package is here. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Wed, 30 Apr 2008 16:38:35 -0000 Message-Id: <20080430163835.31888.11735.malone@potassium.ubuntu.com> I uploaded this fix to the ppa of the ubuntu-quickfix team, which is an open team that, in my mind, should prepare simple fixes to be tested aganst the "current" distribution, that do not seem to harm, while waiting for them to be taken into account by the main distribution developers. Any launchpad user with enough skills to incorporate someone else's patch into an ubuntu package is invited to participate. Clearly, when fixes are incorporated in ubuntu, or if there's a strong enough reason, corresponding packages will be deleted from the ppa. The sources.list entry is here https://edge.launchpad.net/~ubuntu-quickfix/+archive or you can just install individual packages by clicking on debs. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Peter Rhone (prhone-gmail) Date: Sun, 04 May 2008 13:44:54 -0000 Message-Id: <20080504134454.8813.82526.malone@gangotri.canonical.com> Thanks for the debs Vincenzo, unfortunately they didn't help in my case. In fact the display in evince seems to no longer be anti-aliased, and printing quality was not affected. If I select text in evince, the highlighted text is replaced primarily by squares and other unual character, both with and without your deb files. I've included the pdf so you can see what I mean and confirm on your system. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Sun, 04 May 2008 14:29:37 -0000 Message-Id: <20080504142937.23892.11318.malone@gandwana.canonical.com> I see: the fix I incorporated breaks video antialiasing for certain fonts. It solved things in my test-case but not in the one posted by SqRt7744. On my system, both original poppler and the patched version do not even start printing whereas both kpdf and acroread print correctly Haut_A4.pdf. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: vanadium (ftack) Date: Wed, 14 May 2008 14:59:03 -0000 Message-Id: <20080514145903.31491.27275.malone@gangotri.canonical.com> I confirm this issue on Hardy. Installing "cm-super" fixed the display issue. After that, the document that Benjamin Redelings added opens instantaneously. However, printing continues to generate a very low quality bitmapped printout. The problem is there with PDFs created using pdfLatex. I do not have the problem with PDFs generated by ghostscript. I confirm that the problem is with evince only. No issue with Acrobat Reader. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Fri, 06 Jun 2008 12:15:08 -0000 Message-Id: <20080606121508.16359.86893.malone@gangotri.canonical.com> Vanadium: You misunderstood; The problem wasn't that the document OPENED slowly. The problem was that it took 90 seconds to GENERATE A PRINT PREVIEW. 1. This problem of slowness in Print Preview still exists in current Hardy and current Intrepid. 2. The blurriness of the text is still present, but is less severe. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Benjamin Redelings (benjamin-redelings) Date: Fri, 06 Jun 2008 12:23:17 -0000 Message-Id: <20080606122317.16359.10349.malone@gangotri.canonical.com> Edit: Woops. Actually, the blurriness in Print Preview is NOT less severe. It is just as severe as before. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Langasek (vorlon) Date: Thu, 12 Jun 2008 07:55:16 -0000 Message-Id: <20080612075517.16824.60892.malone@gandwana.canonical.com> unfortunately we don't have a handle on the fix for this yet, so I'm deferring the bug since we can't really get this done for .1. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Wed, 24 Sep 2008 18:19:21 -0000 Message-Id: <20080924181921.24214.53541.malone@palladium.canonical.com> I confirm that the bug is still there in intrepid alpha 6. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Fri, 03 Oct 2008 05:29:54 -0000 Message-Id: <20100914164620.4895.8708.launchpad@loganberry.canonical.com> Under Fedora 9 (x86_64), this kind of works for me: The print preview of only one page takes about 60 s, but the quality is okay. If I print this one page into a pdf file, the result is 2.4 MB big, while the original document (270 pages) is 4.5 MB. To open this one pdf-printed file, it takes about 3 mins on my machine. Using: Cairo 1.6.4 1.fc9 Poppler 0.8.1 2.fc9 Evince 2.22.2 1.fc9 But regarding the speed and the size of the file and the speed, I still would not consider this as solved. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Fri, 03 Oct 2008 13:16:03 -0000 Message-Id: <20081003131603.9135.43343.malone@potassium.ubuntu.com> I also confirm that it is still there (updated Alpha 6, amd64) using: libcairo2 1.7.6-0ubuntu1 libpoppler3 0.8.7-1 evince 2.24.0-0ubuntu1 --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Fri, 03 Oct 2008 13:31:01 -0000 Message-Id: <20081003133101.11126.26960.malone@gandwana.canonical.com> Oh, I was wrong: The text in the preview (takes about 1 min to generate) ap= pears blurry only at the beginning. When I zoom in, the quality becomes bet= ter after another 2 mins of waiting. If I print one page into pdf, the generated pdf is 2.4 MB big, the originia= l with 270 pages is only 4.5 MB. Opening this pdf also takes about 8 minute= s, keeping one CPU at 100 %. Printing the whole document into pdf does not work. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Fri, 03 Oct 2008 13:40:46 -0000 Message-Id: <20081003134046.16869.99293.malone@gandwana.canonical.com> der_vegi: I think you wanted to comment upstream. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Fri, 03 Oct 2008 13:55:15 -0000 Message-Id: <20081003135515.1102.33923.malone@palladium.canonical.com> I talked with an upstream developer in IRC. The point is that evince uses libcairo and libcairo did not have support for "user fonts". Now that the new feature is implemented in cairo, somebody must actually make poppler _use_ it. The likely correct upstream bug is http://bugs.freedesktop.org/show_bug.cgi?id=3D17497 --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adrian Johnson (ajohnson-redneon) Date: Sat, 01 Nov 2008 06:18:07 -0000 Message-Id: <20100914164620.4895.21453.launchpad@loganberry.canonical.com> Fix in git. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Sun, 02 Nov 2008 11:28:02 -0000 Message-Id: <20081102112803.5136.43818.malone@potassium.ubuntu.com> the bug has been fixed upstream now --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Felipe Figueiredo (philsf) Date: Sun, 02 Nov 2008 16:11:41 -0000 Message-Id: <1225642301.1259.3.camel@localhost> On Sun, 2008-11-02 at 11:28 +0000, Sebastien Bacher wrote: > the bug has been fixed upstream now >=20 > ** Changed in: poppler (Ubuntu) > Status: Triaged =3D> Fix Committed >=20 In what upstream version will it appear? Will the fix be backported to hardy and/or intrepid? regards FF --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Sun, 02 Nov 2008 16:42:02 -0000 Message-Id: <20081102164202.5136.16429.malone@potassium.ubuntu.com> the next upstream version, what number they will use is an upstream question, the backport depends if the changes can be easily applied to the intrepid version and don't create other issues --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Felipe Figueiredo (philsf) Date: Tue, 04 Nov 2008 07:32:21 -0000 Message-Id: <20100914164620.4895.24327.launchpad@loganberry.canonical.com> (In reply to comment #23) > Fix in git. >=20 how can one pinpoint the patch that fixes this? Could you perhaps attacht it to this bug. Maybe at least the revision in which it appeared in git? Thanks in advance. FF --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adrian Johnson (ajohnson-redneon) Date: Wed, 05 Nov 2008 06:00:41 -0000 Message-Id: <20100914164620.4895.75658.launchpad@loganberry.canonical.com> (In reply to comment #24) > how can one pinpoint the patch that fixes this? Could you perhaps attacht= it to > this bug. Maybe at least the revision in which it appeared in git? The 12 commits on master from 0b5ee897 to 0741a4026. They were also posted to the mailing list. See the archives for the end of Oct/beginning of Nov. You will also need cairo 1.8.2. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Mon, 19 Jan 2009 13:24:07 -0000 Message-Id: <20090119132407.23324.99806.malone@potassium.ubuntu.com> the bug should be fixed in jaunty, could somebody try and confirm if that's working correctly now? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Mon, 19 Jan 2009 14:48:13 -0000 Message-Id: <20090119144814.14871.55305.malone@gandwana.canonical.com> What packages should I backport to test it in intrepid? Is it unfeasible? I backported popler and evince using prevu but results remain the same, however I suspect that evince is using some .*gnomeprint.* package to print pdfs. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Mon, 19 Jan 2009 15:21:26 -0000 Message-Id: <20090119152126.14871.94671.malone@gandwana.canonical.com> The point is that the backported evince (using prevu) is using libpoppler3 instead of libpoppler4. Is there a quick way to have the backported evince use the backported libpoppler4 or to also build libpoppler3 from the backported poppler from prevu? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Felipe Figueiredo (philsf) Date: Mon, 19 Jan 2009 15:45:53 -0000 Message-Id: <385d1e010901190745w79047966u8143d41820d40ed3@mail.gmail.com> You can recompile evince, same version you're using without any changes to the source. It will be recompiled to use the newest poppler. I did this to use poppler3 in hardy without any issues. On Mon, Jan 19, 2009 at 1:21 PM, Vincenzo Ciancia wr= ote: > The point is that the backported evince (using prevu) is using > libpoppler3 instead of libpoppler4. Is there a quick way to have the > backported evince use the backported libpoppler4 or to also build > libpoppler3 from the backported poppler from prevu? > > -- > [gutsy] [regression] Evince has very bad quality when printing pdf files. > https://bugs.launchpad.net/bugs/150187 > You received this bug notification because you are a direct subscriber > of the bug. > --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Mon, 19 Jan 2009 15:52:58 -0000 Message-Id: <20090119155258.14871.42104.malone@gandwana.canonical.com> dunno how prevu works but rebuilding after installing the new libpoppler should work correctly --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Mon, 19 Jan 2009 17:24:23 -0000 Message-Id: <20090119172423.25588.6345.malone@palladium.canonical.com> I now have all the packages that are generated by the source package poppler, version 0.10.3-0ubuntu1, and recompiled intrepid's evince. I checked using ldd that evince is using the new libraries. However, the problem is still the same. The document called "speciation_state_correlation.pdf", attached to this bug report, when printed to a pdf file via evince, occupies 9.7 megabytes, and has terrible quality. The document indeed contains type 3 fonts. This bug does not seem solved to me. Maybe evince passes the pdf on to other libraries that maybe use the old libpoppler? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Mon, 19 Jan 2009 17:52:57 -0000 Message-Id: <20090119175257.23324.71032.malone@potassium.ubuntu.com> I am now typing from a jaunty alpha 3 live usb pen. I upgraded the system, I correctly got an update of evince and libpoppler. But the bug is still there. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Mon, 19 Jan 2009 20:21:21 -0000 Message-Id: <20090119202121.6748.48017.malone@palladium.canonical.com> I just booted into the live system of daily-live 20090116.3 (amd64). Still a problem: Printing one page (the same as I tested above) as .pdf produces a 2.1 M file. Looking at it in evince shows blurry equations and text, though after 3-4 min(!) the quality gets better. Does it take so long to render? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Mon, 09 Mar 2009 09:42:26 -0000 Message-Id: <20100914164620.4895.54874.launchpad@loganberry.canonical.com> Using cairo 1.8.6 and poppler 0.10.4 this is still a problem: A pdf- print of one page from a 250 page pdf document with 4.5 MB generates a 2.1 MB file that takes about 2-3 minutes opening until it appears in a good quality. Can anyone confirm this? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: der_vegi (m-may) Date: Mon, 09 Mar 2009 16:44:15 -0000 Message-Id: <20090309164416.6970.17060.malone@gandwana.canonical.com> Still an issue on a daily-live 20090306, all updates applied. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adrian Johnson (ajohnson-redneon) Date: Wed, 11 Mar 2009 08:04:39 -0000 Message-Id: <20100914164620.4895.10758.launchpad@loganberry.canonical.com> (In reply to comment #26) > Using cairo 1.8.6 and poppler 0.10.4 this is still a problem: A pdf-print= of > one page from a 250 page pdf document with 4.5 MB generates a 2.1 MB file= that > takes about 2-3 minutes opening until it appears in a good quality. Can a= nyone > confirm this? The fix is not in a released version. You will have to wait for 0.12 or build from git master. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adrian Johnson (ajohnson-redneon) Date: Wed, 11 Mar 2009 22:05:20 -0000 Message-Id: <20090311220521.5899.197.malone@gandwana.canonical.com> Vincenzo Ciancia wrote: > I now have all the packages that are generated by the source package popp= ler, version 0.10.3-0ubuntu1, and > recompiled intrepid's evince. I checked using ldd that evince is using th= e new libraries. However, the problem is still > the same. The fix is not in 0.10.x. You need to wait for 0.12 or apply the 13 patches= dated 2008-10-31, 2008-11-01, and 2008-11-23 from http://cgit.freedesktop.org/poppler/poppler/log/?qt=3Dauthor&q=3DAdrian --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Thu, 19 Mar 2009 15:29:35 -0000 Message-Id: <20090319152935.10906.85160.malone@palladium.canonical.com> Could someone in ubuntu comment on the patches? These should be applied as soon as possible. Please consider this bug a bit more: I reported it in 2007 and we have a patch here! --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Till Kamppeter (till-kamppeter) Date: Thu, 19 Mar 2009 15:40:21 -0000 Message-Id: <20090319154021.31988.15296.malone@potassium.ubuntu.com> Milestoned it, a bug with patches already available should get fixed in Jaunty. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Felipe Figueiredo (philsf) Date: Thu, 19 Mar 2009 15:52:58 -0000 Message-Id: <20090319155259.31371.86499.malone@gandwana.canonical.com> It looks from the patch that it requires cairo 1.8.2, so it would require a non-trivial backport for both hardy and intrepid. Could someone who actually understands it confirm this, and decide if this blocks an eventual SRU? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Thu, 19 Mar 2009 21:28:52 -0000 Message-Id: <20090319212853.12318.67441.malone@gangotri.canonical.com> there is not a patch there is a lot of non trivial patches rather, not really something for jaunty --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Fri, 20 Mar 2009 12:27:25 -0000 Message-Id: <20090320122725.9853.94972.malone@potassium.ubuntu.com> Thanks for your comment. Is it already taken for granted that the current gnome head will be in jaunty+1? If so we're all set, it is just a matter of waiting. If not it should be milestoned for jaunty+1 then. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Sun, 28 Jun 2009 18:52:38 -0000 Message-Id: <20090628185238.12063.30413.malone@potassium.ubuntu.com> This bug is fixed in karmic. Together with the discovery of the impose+ package for scaled booklet printing, I got finally rid of acrobat reader on my computer. Thanks. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Mon, 29 Jun 2009 09:12:09 -0000 Message-Id: <20090629091210.12453.569.malone@gangotri.canonical.com> the issue is fixed in karmic now --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Tue, 30 Jun 2009 11:58:25 -0000 Message-Id: <20090630115825.9602.34457.malone@gangotri.canonical.com> Today I printed the "subgroup(group theory)" page from wikipedia using firefox, to a pdf file, which is small and vectorial. Then re-printed it via evince for reasons that are not relevant, and the obtained pdf is big, bitmapped, and horribly looking. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Tue, 30 Jun 2009 11:58:57 -0000 Message-Id: <20090630115857.9602.28406.malone@gangotri.canonical.com> --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Tue, 30 Jun 2009 12:00:06 -0000 Message-Id: <20090630120007.9602.78709.malone@gangotri.canonical.com> The re-print from evince is terrible, the one from okular looks good, but the formula on the third page is obscured. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Tue, 30 Jun 2009 12:02:20 -0000 Message-Id: <20090630120220.15890.24975.malone@gandwana.canonical.com> So, my mood is below my shoes for this bug, because it's in the most important program for a scientist: the default pdf viewer. And it makes absolutely necessary to install a proprietary program to do the most basic activity people perceived doable with computers: printing, like with typewriters. It's free knowledge, converted from a free format to another free format, but I need a proprietary program to get a printout. So please, can somebody help me understand if the cases above are the same bug or not? --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: wolf87 (ablocker) Date: Tue, 30 Jun 2009 13:04:02 -0000 Message-Id: <20090630130403.28335.25105.malone@potassium.ubuntu.com> Replicated bug on Jaunty without backports. It appears to be an issue with unpatched systems. Testing patched now (will be only system changes). --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Till Kamppeter (till-kamppeter) Date: Tue, 30 Jun 2009 13:10:17 -0000 Message-Id: <20090630131017.22127.39844.malone@palladium.canonical.com> I have downloaded the PDF and tried evince in Karmic. I printed into a PDF file with the "Print to file" functionality of evince, so it is really evince and not the CUPS filter chain. Pages 1 and 4 get completely bitmapped whereas pages 2 and 3 are treated correctly as text and vector graphics. It seems that page 2 and 3 contain something which makes Poppler bitmap the whole page. Seems that there is some little item inside which Poppler cannot treat as vector graphics and therefore Poppler bitmaps the whole page. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Tue, 30 Jun 2009 13:52:48 -0000 Message-Id: <1246369968.16433.13.camel@frattaglia> Thanks, do you think this is the same bug that seemed fixed or should I open a new one? I guess the current bug had to do with fonts but I do not understand very well all the connections between fonts, images and so on in pdf. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adrian Johnson (ajohnson-redneon) Date: Wed, 01 Jul 2009 12:08:21 -0000 Message-Id: <20090701120821.25664.36.malone@gandwana.canonical.com> The low quality printing in your PDF is a different bug. This bug is about Type 3 fonts being printed as a bitmap. The PDF you attached has no Type 3 fonts. The reason pages 1 and 4 of your PDF are printed as a bitmap are: - Firefox is using cairo operators that are not natively supported by PDF on page 1 and 4. I don't think there is any reason that Firefox needs to use anything other than CAIRO_OPERATOR_OVER when printing so I consider this a bug in Firefox. - As a result cairo embeds a fallback image in the PDF for the region drawn with operators not supported by PDF. But the bounding box of the PDF pattern used to draw the fallback image is set to the page size instead of the image size. This is a bug in cairo. - When poppler is used to print the PDF via the cairo backend the image becomes a full page image due to the pattern bounding box being set to the page size. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Wed, 01 Jul 2009 12:57:00 -0000 Message-Id: <20090701125701.26501.75329.malone@potassium.ubuntu.com> I reported a new bug, please triage it and subscribe if appropriate. https://bugs.edge.launchpad.net/ubuntu/+source/poppler/+bug/394266 --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Mon, 20 Jul 2009 15:30:07 -0000 Message-Id: <20090720153007.24722.24323.malone@gandwana.canonical.com> is that issue still there using current karmic? evince nows print using pdf dirrectly --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vincenzo Ciancia (vincenzo-ml) Date: Mon, 20 Jul 2009 16:25:56 -0000 Message-Id: <20090720162556.4915.89498.malone@palladium.canonical.com> Fixed in karmic and thanks all again. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Mon, 20 Jul 2009 17:59:48 -0000 Message-Id: <20090720175948.4915.5784.malone@palladium.canonical.com> dropping milestone and assignee, it's a low priority target of opportunity if somebody comes with a backported change for hardy --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: SanDiego (ergut) Date: Tue, 01 Dec 2009 23:02:34 -0000 Message-Id: <20091201230234.15403.27098.malone@wampee.canonical.com> Installing "cm-super" on Hardy fixed it for me. Thanks Mark. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bart Verwilst (verwilst) Date: Fri, 09 Mar 2012 11:50:09 -0000 Message-Id: <20120309115009.25623.30844.malone@gac.canonical.com> In Oneiric, I still can't print pdfs with Evince that aren't blurred. Works perfectly when printing with acroread. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Till Kamppeter (till-kamppeter) Date: Fri, 09 Mar 2012 19:26:04 -0000 Message-Id: <20120309192604.8595.47149.malone@chaenomeles.canonical.com> Bart, probably your problem is not the one reported here, as the reported bug is already fixed. Please open a new bug with the PDF files attached which come out in bad quality when printed with evince. Please also follow the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems, especially the sections "CUPS error_log" and "Capturing print job data". Note that evince re-renders the PDF file when printing it, so that captured print job data is not the same as the original file. --===============7638371431175314561== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Rolf Leggewie (r0lf) Date: Sun, 23 Nov 2014 15:09:34 -0000 Message-Id: <20141123150934.18143.45764.malone@chaenomeles.canonical.com> Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix". --===============7638371431175314561==--