Red Hat Bugzilla – Bug 55547
ljet4 prints quarter page at 300 dpi
Last modified: 2008-05-01 11:38:01 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.5+) Gecko/20011031 Description of problem: I am using an HP LaserJet4L with the ljet4 driver. When using 300 dpi resolution only the top left quarter of the printtool test page is displayed covering the full page. If set at 150dpi the test page prints correctly. If I use the ljet3 driver the test page is correct. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.select hp/ljet4l/ljet4 driver from printtool 2.select 300 dpi printer option 3. Additional info:
Omni-0.5.0-4, printconf-0.3.52-1 ghostscript-6.51-16, foomatic-1.1-0.20011018.3 I have a Canon S450, and using BJC6000 (the S450 is reported to be the same as BJC6000, selecting S450 results in fewer options, but does not change anythigng else): With the omni driver, only a quarter of the page is printed, regardless of the resolution selected. With the stp and upp drivers, lpdomatic fails with the following error message: IF filter 'mf_wrapper' filter msg - 'Couldn't exec at /usr/sbin/lpdomatic line 629.' at 2001-11-05-23:53:26.844 ## A=<NULL> number=198 process=3215 IF filter 'mf_wrapper' filter msg - 'tail process done writing data to *main::STDOUT' at 2001-11-05-23:53:26.846 ## A=<NULL> number=198 process=3215 IF filter 'mf_wrapper' filter msg - 'closing *main::KID3' at 2001-11-05-23:53:27.459 ## A=<NULL> number=198 process=3215 IF filter 'mf_wrapper' filter msg - 'Error closing pipe to at /usr/sbin/lpdomatic line 422, <STDIN> line 83564.' at 2001-11-05-23:53:27.459 ## A=<NULL> number=198 process=3215
The ljet3 driver is OK as a workaround, but it's still not ideal: the margins are wrong, so the printing ends up too high on the page, and I usually get a small amount of corruption (i.e. a few lines of pixels) near the bottom of the page.
This has similaries to bug #40809.
Also to bug #58302.
*** Bug 40809 has been marked as a duplicate of this bug. ***
Has everyone here applied all the printing-related updates to date?
Aargh. Sorry - was on foomatic-1.1-0.20011018.6. Must have missed the announcement for 20011018.7. Upgrading to that has fixed it. Thanks very much. And sorry...
Great, thanks!