Bug 661814 - Foomatic/pxlmono very slow
Summary: Foomatic/pxlmono very slow
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ghostscript
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 670089 675993 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-09 17:40 UTC by GeoffLeach
Modified: 2011-10-07 16:19 UTC (History)
5 users (show)

Fixed In Version: ghostscript-9.04-3.fc15
Clone Of:
Environment:
Last Closed: 2011-10-07 15:43:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Offending .jpg. It's NOT the only one that has a problem (35.27 KB, image/jpeg)
2010-12-09 17:40 UTC, GeoffLeach
no flags Details
debugging output (907.63 KB, text/plain)
2010-12-09 21:41 UTC, GeoffLeach
no flags Details

Description GeoffLeach 2010-12-09 17:40:14 UTC
Created attachment 467806 [details]
Offending .jpg. It's NOT the only one that has a problem

Description of problem: In fact, unable to print just the .jpg. Sample attached is not the only one that causes the problem


Version-Release number of selected component (if applicable):
foomatic-db-4.0-20.20100819.fc14.noarch

How reproducible: always


Steps to Reproduce:
1.send html containing .jpg reference (or just the raw .jpg) to printer (LaserJet 1300, B&W) from FireFox 3.6.12
2.
3.
  
Actual results:
PCL XL error
  Subsystem: KERNEL
  Error: IllegalTag
  Operator: 0x1b
  Position: 356808


Expected results:
Prints. Works under F13

Additional info:
FireFox renders the .jpg without difficulty

Comment 1 Jiri Popelka 2010-12-09 19:49:03 UTC
Can you print that jpg directly with 'lpr opgrat-email.jpg' ?

Can you attach an output from printing troubleshooter ?
https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter
When it asks you to print test page, print the .jpg either with lpr command (if that also causes the problem) or from firefox.

Comment 2 GeoffLeach 2010-12-09 21:41:17 UTC
Created attachment 467854 [details]
debugging output

Printed correctly after 15-20 minutes.  Sending via lpr printed OK.

Comment 3 GeoffLeach 2010-12-10 18:31:06 UTC
Under foomatic-db.noarch 0:4.0-23.20101123.fc14 jpg prints but takes an unacceptably long (~15 min) time. I'm not sure whether this might have been the case with the earlier version. I never waited that long.

Comment 4 Jiri Popelka 2010-12-13 15:51:42 UTC
(In reply to comment #2)
> Created attachment 467854 [details]
> debugging output
> 
> Printed correctly after 15-20 minutes.  Sending via lpr printed OK.

So this output is from printing via lpr ?
With foomatic-db-4.0-20.20100819.fc14 or foomatic-db-4.0-23.20101123.fc14 ?

Comment 5 GeoffLeach 2010-12-29 23:05:06 UTC
Output is via lpr. With foomatic-db-4.0-23.20101123.fc14.

It's worse with foomatic-4.0.5-1.fc14.i686. Straight text works fine, but non-textual output (google map, for example) takes 20 min where previously it took a minute or so.

Comment 6 GeoffLeach 2011-01-01 17:39:19 UTC
The driver installed for the HP LaserJet 1300 by default (presumably by the foomatic RPM is pxlmono. Turns out that's the wrong choice. Correct choice is Postscript

Comment 7 Tim Waugh 2011-01-04 11:23:19 UTC
This issue will be fixed in system-config-printer-1.3.  The issue is that we can't be sure the printer supports PostScript unless we see that it says so in its IEEE 1284 Device ID.

Comment 8 Tim Waugh 2011-01-10 12:44:24 UTC
Upstream report STR #3405 looks like it might be relevant to this:
  http://cups.org/str.php?L3405

I'll try changing the buffer size in the usb backend to 512 bytes instead of 8192 bytes.  Once I've built a package with that change I'll ask you to try it out using the pxlmono driver again.

Comment 9 Tim Waugh 2011-01-10 16:44:08 UTC
Would be great if you could try this package:
  http://koji.fedoraproject.org/koji/buildinfo?buildID=213515

Download all the packages for your architecture and then run this command as root in the directory they are in:

yum update --nogpgcheck ./cups-*.x86_64.rpm

After doing this, please try printing using the pxlmono driver and see if the speed is any different.

Comment 10 Tim Waugh 2011-01-17 15:42:53 UTC
*** Bug 670089 has been marked as a duplicate of this bug. ***

Comment 11 Joachim Backes 2011-01-17 16:12:37 UTC
I was duplicated from BZ #670089, and I checked my problems after having updated to cups-1.4.6-2.fc14.i686.rpm and cups-libs-1.4.6-2.fc14.i686.rpm, I did reset my lexmark network printer to foomatic/pxlmono, then I tested to print http://www.rhrk.uni-kl.de, but, I'm sorry, nothing printed (behaviour as before installing then 2 rpm's). So my problem does not seem to be solved. Going back to foomatic/ljet4.

Comment 12 Tim Waugh 2011-01-18 17:26:41 UTC
Printing that image through to a Foomatic/pxlmono PPD results in a 3.3Mb output file, compared to 0.6Mb for Foomatic/ljet4.

The reason the pxlmono driver is recommended for this printer is given in the foomatic-db ChangeLog:

2010-07-14  Till Kamppeter <till.kamppeter>

        * printer/HP-LaserJet_1200.xml, printer/HP-LaserJet_1220.xml,
          printer/HP-LaserJet_1300.xml, printer/HP-LaserJet_1320.xml,
          printer/HP-LaserJet_3390.xml, printer/HP-LaserJet_3392.xml:
          Recommend the "pxlmono" driver instead of HPLIP PostScript, these
          printers do not have enough memory for high-resolution PostScript
          printing.

Comment 13 GeoffLeach 2011-01-18 18:02:38 UTC
Hmmmm ... this would seem to raise the question of how much memory. My experience with a standard-memory 1300 is that printing a relatively small JPG takes an unacceptable length of time, whereas with HPLIP it's virtually instantaneous. And that applies to a page with any graphics. As we're back to foomatic, I would suggest that  pxlmono needs to be evaluated _and_ the default driver returned to  HPLIP PostScript in the interim.

Comment 14 Tim Waugh 2011-01-19 16:44:06 UTC
Reported upstream (printing-foomatic).

I've updated system-config-printer on the master branch so that it avoids pxlmono (it's hard to do this on the 1.2.x branch) in commit f4dad9b.

Comment 15 Alexei Panov 2011-02-02 22:19:02 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 16 Jiri Popelka 2011-02-08 16:02:43 UTC
*** Bug 675993 has been marked as a duplicate of this bug. ***

Comment 17 Tim Waugh 2011-10-07 15:43:26 UTC
Exception removed upstream because the original problem causing large output file sizes for pxlmono was in ghostscript, and this bug is fixed in 9.04.  (See Launchpad #821818.)


Note You need to log in before you can comment on or make changes to this bug.