GNOME Bugzilla – Bug 559989
Eye of gnome printing multiple copies bug
Last modified: 2012-03-07 11:34:18 UTC
Please describe the problem: Ubuntu 8.10, eog 2.24.1, right after upgrading to Intrepid (fresh online upgrade) Printer: HP LaserJet 1022, HPLIP I opened a png image and wanted to print out in 2 copies. 2 papers came out from the printer, but the first was only an empty sheet of paper. I tried more times with more images. I used this function with Hardy (almost twice a week), the PC the printer etc. are the same. Under Hardy it worked well, this bug appeared after upgrading to Intrepid. Steps to reproduce: 1. open a png image (or I guess other types also give the same results) 2. File -> Print, select more copies, e.g. 2 3. Print it out Actual results: Two sheets come out from the printer, but the first is empty, only the second has the image (if you selected 2 copies for printout) Expected results: Two same sheet with the image Does this happen every time? yes Other information: did not try with other distro, only the fresh Ubuntu Intrepid Also reported at Launchpad: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/293010
Works for me. Deskjet 6940 + HPLIP Is there something special about the images (size?).
I have the same problem. I am using a fresh install of Ubuntu 8.10 Intrepid Ibex and my printer is an Epson Stylus Photo R230. This is _not_ an issue with the CUPS driver. When I print from the terminal using: lp -d Stylus-Photo-R230 -n 2 graphicsfile.png I get two copies, as I should. Also, if I open the same file in OpenOffice Drawing and print from OpenOffice, I get my two copies. However, I run into this bug when I print from Eye Of Gnome 2.24.1 _and_ Gimp 2.26. I've also reported this issue at LaunchPad: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/293010
Maybe a distribution specific bug? First of all, as far as I remember, there are no printing related changes in eog between 2.22 and 2.24. Secondly, this happening with other GTK+ applications moves the problem out of eog's scope. I'm moving this to GTK+, but I'm suspecting this to be actually an Ubuntu issue.
sipiatti, mondray: Is this still a problem for you in a recent version? If so, which gtk version do you use nowadays?
NEEDINFO as per my last question.
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!