Hide Forgot
Description of problem: hp-deskjet-2050_j510_series crops A4 documents Version-Release number of selected component (if applicable): hplip-3.11.1-3.fc14.i686, as far as I can tell, it also applies to the production version How reproducible: Always Steps to Reproduce: 1. Install the test version of hplip i.e hplip-3.11.1-3.fc14.i686 2. Connect the printer, and alter printer settings to A4 3. Print a test page from the printer setup Actual results: The page is cropped to about letter size, i.e missing approximately 20 m.m. at the bottom of the page. If the printing was done in landscape mode the print is cropped the same amount at the left side of the landscape print. Expected results: A full A4 test page page where the testpage border is visible close to the edge of the page on all 4 sides of the printed page. Additional info: I have tried to change the PPD file but I'm not sure what the correct values should be. If I grep the PPD for A4 I have the following A4 related settings: *PageSize A4/A4 210x297mm: "<</PageSize[595.44 841.68]/ImagingBBox null>>setpagedevice" *PageRegion A4/A4 210x297mm: "<</cupsInteger0 26/PageSize[595.44 841.68]/ImagingBBox null>>setpagedevice" *ImageableArea A4/A4 210x297mm: "9.00 41.04 586.44 837.36" *PaperDimension A4/A4 210x297mm: "595.44 841.68"
I forgot to mention that the ppd used was the hp-deskjet_2050_j510_series.ppd. Using the hp-deskjet_2050_j510_series-hpijs.ppd instead gives better result, but there is still a about a millimeter missing, and on Fedora this whould require the hplip packages to be recompiled using the configure --enable-foomatic-rip-hplip-install flag.
Please run the printing troubleshooter: https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter and attach the troubleshoot.txt file you end up with.
Created attachment 489854 [details] troubleshoot.txt from hplip-3.11.1-3.fc14.i686 This resulted in a testpage, with about "letter" size even though A4 was chosen, leaving the bottom of the page blank.
Letter size is much shorter than that. You should see this on the test page: Media Limits: 0.12 x 0.57 to 8.15 x 11.63 inches 3 x 14 to 207 x 295 millimeters i.e. the lower-left boundary is 3mm in from the side and 14mm from the bottom edge. This is because the hpcups PPD says that the hardware limit is 41.04 points (72 points make an inch) from the bottom edge: *HWMargins: 9 41.040000915527 9 4.320000171661 If this is incorrect you could try adjusting the '41.04' value there and in the ImageableArea A4 setting to see how low it can safely be set. You may need to restart cups after modifying the PPD. For reference, the hpijs PPD has '36' for that value.
It doesn't seam to matter what value I for the HWMargin use. The result is the same. I'm starting to wonder if I'm editing the right file. I have tried to edit /usr/share/cups/drv/hp/hpcups.drv line 7412, but I'm not sur how to change ImagebleArea as there, as far as I can see, are no examples on how to do that.
Edit the PPD in /etc/cups/ppd/, but change *both* the HWMargins *and* the ImageableArea values, and restart cups afterwards.
(In reply to comment #7) > Edit the PPD in /etc/cups/ppd/, but change *both* the HWMargins *and* the > ImageableArea values, and restart cups afterwards. Done that, and it still doesn't matter what values I set. The cropping remains the same regardless what value I use.
Created attachment 490329 [details] My non working /etc/cups/ppd/HP-Deskjet-2050-J510-series.ppd file
The following edit seams to do the trick: - *PageSize A4/A4 210x297mm: "<</PageSize[595.44 841.68]/ImagingBBox null>>setpagedevice" + *PageSize A4/A4 210x297mm: "<</cupsInteger0 26/PageSize[595.44 841.68]/ImagingBBox null>>setpagedevice" Suggested by Ani Balakrishnan on the HPLIP issuetracker https://bugs.launchpad.net/hplip/+bug/748303
As this fix was included in HPLIP 3.11.5, I think this test update package should fix the problem: https://admin.fedoraproject.org/updates/hplip-3.11.5-1.fc14 Would you mind giving it a go? yum --enablerepo=updates-testing update 'hplip*' 'hpijs*' 'libsane-hp*' Create a new queue and see if the problem is now fixed. Thanks in advance...