After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 537615 - Image is printed in the wrong size (too large)
Image is printed in the wrong size (too large)
Status: RESOLVED DUPLICATE of bug 524615
Product: GIMP
Classification: Other
Component: General
2.4.x
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2008-06-10 15:25 UTC by jusola
Modified: 2008-10-30 20:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot of used settings (16.06 KB, image/png)
2008-06-10 15:27 UTC, jusola
Details

Description jusola 2008-06-10 15:25:06 UTC
Please describe the problem:
I tried to print a 400x426 jpeg with HP PhotoSmart 2575 by setting the size to 100x106.5mm and it was printed at approximately 12 PPI resolution (the upper left corner, maybe 90 x 130 pixels, filled the whole portrait A4).


Steps to reproduce:
In Image Settings tab, I set the width to 100 millimeters (and the height was then automatically set to 106.50 mm, x and y resolution to 101.6 pixels/in).
I set Position to the following values: Center None, left 20.00, top 20.00.
Ignore Page Margins was left unchecked.
I checked from Adjust Page Size and Orientation that the page size was A4.

Actual results:
Only a small part of the image was printed at a very low resolution filling the entire A4.

Expected results:
The image is printed in the upper left corner of the A4 at a size of 100x106.5 mm.

Does this happen every time?
Did not repeat this...

Other information:
Windows XP SP2 Finnish, Gimp 2.4.6 English.
Comment 1 jusola 2008-06-10 15:27:46 UTC
Created attachment 112479 [details]
screenshot of used settings
Comment 2 Martin Nordholts 2008-06-10 15:40:17 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 524615 ***