Red Hat Bugzilla – Bug 121302
Gedit always prints a blank page after printing the document
Last modified: 2007-11-30 17:10:40 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312 Description of problem: Each time I print a document using gedit, it is printed correctly apart from the fact that an additional blank page is always printed. For example, if I print a 4 page document, I get 4 pages full of text (the actuall document) and a fifth blank page. Version-Release number of selected component (if applicable): gedit-2.6.0-4 How reproducible: Always Steps to Reproduce: 1.Print a document in gedit Actual Results: The document is printed correctly, but an additional blank page is "printed". Expected Results: Well, the additional blank page shouldn't be printed. Additional info: It's from Fedora Core 2 test2
The error (if there was an error actually) would not be from gedit, but rather from the internal routines it used to print the document. e.g GTK+. I think Fedora uses CUPS as a printing daemon, try to locate the log files it generates (maybe in /var/spool/ ?).
Works for me. I printed a two page document with gedit, and two pages came out. It used CUPS to print to a Samsung printer shared with Win XP over samba. Gedit 2.6 and Fedora Core 2.
Is the blank page shown in print preview? Do you have the same issue with other apps (for example gpdf)?
No, the blank page doesn't appear in the print preview, and doesn't appear if I print to a PDF file either. And from other apps I don't have this problem (I tried with xpdf, OOO, mozilla and gimp among others).
Can you try with another app using libgnomeprint ? Gpdf for example
Actually better evolution or gnumeric, gpdf is sort of special.
I have the same problem with both Evolution and Gnumeric. So I guess gnome-print is the culprit...
Reassigning then
Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match.
This is fixed in FC4, closing