GNOME Bugzilla – Bug 783416
A blank page output when print a specific JPEG file
Last modified: 2021-06-19 08:46:00 UTC
Please describe the problem: A blank page output when print a specific JPEG image file. I have a JPEG image file "Penguins_1200_half.jpg" that is 12773x4922 pixels. When I open the image with Image Viewer and choose print, the file cannot be printed correctly, a blank page is output by the printer. The file in question is available for your perusal at attachment. Product Version details: Image Viewer 3.24.0 Distribution/Version: Ubuntu 17.04 Steps to reproduce: 1. Open the file with Image Viewer. 2. Print the file. Actual results: The file cannot be printed correctly, a blank page is output by the printer. Expected results: The file should print as it is displayed on the preview. Does this happen every time? Yes Other information: 1. This problem only occurs on Ubuntu 17.04. It does not occurs on Ubuntu 16.04, CentOS 7.3 and OpenSUSE Leap 42.2. 2. On Ubuntu 17.04, this problem does not occurs when open the file with "Shotwell(0.22.0)". 3. This problem is occurs only when the JPEG file "Penguins_1200_half.jpg" is printed. Other JPG files are printed, the result becomes OK.
Created attachment 353159 [details] The JPEG file that occures the problem
Created attachment 353160 [details] The JPEG file that occures the problem
The size of the JPEG file is more than a single upload attachment size limit, so divided into two compressed packages.
Hmm, eog's printing code is unchanged since GNOME 3.8, so I guess the issue is probably somewhere further down the printing pipeline (libcairo, CUPS, the printer driver, ???). Do you see any difference between the different versions if you select to print the image into a PDF file instead of sending it to the printer? IIRC, the PDF output is pretty much the same that is forwarded to the printing daemon.
(In reply to Felix Riemann from comment #4) > Hmm, eog's printing code is unchanged since GNOME 3.8, so I guess the issue > is probably somewhere further down the printing pipeline (libcairo, CUPS, > the printer driver, ???). > > Do you see any difference between the different versions if you select to > print the image into a PDF file instead of sending it to the printer? IIRC, > the PDF output is pretty much the same that is forwarded to the printing > daemon. Hmm, I'm very sorry to reply to you after so long time. I pause the print queue and obtain the Image Viewer generated print data (d00XXX-001(XXX: Job's No.)) in /var/spool/cups. This is a pdf format file, and I have confirmed that is a blank page open with Document Viewer (Evince). This is what makes me think this is an Image Viewer's bug. After you tell me that eog's printing code is unchanged since GNOME 3.8, I re-confirmed the Image Viewer generated print data again. This time I open the data with gedit, and found the creator of PDF data is Cairo (Ver.1.14.8). For details, please refer to the attachment “d00275-001” Excerpt: << /Creator (cairo 1.14.8 (http://cairographics.org)) /Producer (cairo 1.14.8 (http://cairographics.org)) >> So I think the issue is probably caused by Cairo. If that is correct, how should I deal with this bug report? Can you help me to transfer this bug report to Cairo? Or I re-signed a bug report at https://bugs.freedesktop.org/? By the way, Can you tell me how to print the image into a PDF file?
Created attachment 356684 [details] The Image Viewer generated print data
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/eog/-/issues/ Thank you for your understanding and your help.