GNOME Bugzilla – Bug 312757
Evince CVS HEAD strange issues when printing exactly one page.
Last modified: 2006-04-05 04:47:08 UTC
I have been encountering some weirdness with recent version of Evince. But I tend to believe that this is a libgnomeprint/ui/ libgnomecups issue but I am not sure so I file it here and forward a report to the libgnomeprint people too. I have a document that when loaded looks like under >>> PICTURE1 <<<. When I now want to print exactly the first page and I select a range from 1 to 1 in the libgnomeprintui dialog I end up getting a printout that looks like under >>> PICTURE4 <<< please pay attention to the looks of the font. I tested around a bit and printed the same document and only the first page using ghostscript and kpdf and the printout was ok. I experimented around and used libgnomeprint/ui to save this document COMPLETELY as PS into a file named output.ps please see >>> PICTURE2 <<<. When the entire document got saved the output looked like >>> PICTURE3 <<< well it was ok. Then I saved the same document again using libgnomeprint/ui again as PS file and again as output.ps but only the first page (selecting range 1 to 1) and it ended up like under >>> PICTURE4 <<< the same as my printout. I am also getting an warning output like this: galaxy@ulixys:~ > evince /.quader/.cdram/mnt/stuff/CTRAPS.PDF (evince:1864): GnomePrintCupsPlugin-WARNING **: iconv does not support ppd character encoding: ISOLatin1, trying CSISOLatin1 galaxy@ulixys:~ > I also get the same output with gedit and other programs that use libgnomeprint/ui. There is no font issues or anything, I already checked that one up. Please have a look and in doubt forward this error report to the correct people.
Created attachment 50314 [details] PICTURE1
Created attachment 50315 [details] PICTURE2
Created attachment 50316 [details] PICTURE3
Created attachment 50317 [details] PICTURE4 Ok and here the last picture. I know that this has been happening recently, so only one of the recent changes either in EVINCE (which I doubt) or in libgnomeprint/ui libgnomecups (which I believe more) can be the cause.
I filed a bug http://bugzilla.gnome.org/show_bug.cgi?id=312758
*** Bug 312758 has been marked as a duplicate of this bug. ***
The warning is ignoreable, but you results are worrying. I'd like to see - the input file - the resulting ps & pdf files when printing jsut the first page.
Created attachment 52092 [details] The file that causes this issue The file is called 'CTRAPS.PDF'. But I also got this problem with other *.pdf files that I wanted to print exactly one page from.
Created attachment 52093 [details] PICTURE5 I updated Evince and Poppler and now I even get the *.pdf file rendered like this. Look PICTURE1 and now look at this one PICTURE5. But with older Evince PICTURE1 was ok, and printout of the whole thing was ok too, but printing one page results in the stuff that looks like PICTURE5.
Created attachment 52094 [details] output.ps And here exactly the first page of above document printed into a postscript file. Look how's it looking.
Reopening as Jody's request has been answered.
Same thing here with evince 0.4.0 and poppler 0.4.2
*** Bug 317957 has been marked as a duplicate of this bug. ***
Can we see some progress in this area ? It's quite annoying when using Evince to print out letters or stuff for work/school or university.
Can you try the patch from https://bugs.freedesktop.org/show_bug.cgi?id=4555 please (or try poppler 0.4.3)? This is just for the print problem, not the PICTURE5 problem, please try with an evince/poppler that doesn't have the PICTURE5 problem
Setting to NEEDINFO. Ali: Maybe you could try out poppler 0.4.3 or later?
Hi, I am using Poppler 0_4_X branch at the moment, I wasn't able to test whether the printing issues have been solved due to my short time recently. But as a sidenote. I am not able to compile Poppler from HEAD. I run into big errors running the autogen.sh file to generate a running configure file. It usually throws out macros not found issues such as QT_blah not found. or JPEG_blah not found during the process of building the configure file. I think some KDE guy totally messed up the entire configure thing.
It looks like it works. Did some printouts today, but I was in a hurry so I need to reinvestigate a bit more and report back. Thanks for the patience (I am stuck in a 65 hrs/week job as java-Engineer at a large and top 50 corporate)!
Ok, thanks to Ali for report and testing.