[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#218910: marked as done (cupsys: Excessively slow printing to LPD/JetDirect socket)



Your message dated Sun, 15 Jul 2007 22:52:53 +0300
with message-id <11fae7c70707151252w5bdc90cei3ecf8a91ea9e992e@mail.gmail.com>
and subject line [Pkg-cups-devel] Bug#218910: cupsys: QA response: bug still present but can be easily worked around
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: cupsys
Version: 1.1.19final-1.4
Severity: normal


Hi there!

I have recently acquired an old HP JetDirect card and put it in my
LaserJet 4 Plus. Although printing works perfectly to the printer by
setting it up as an LPD or JetDirect/AppSocket printer, it is far slower
than it should be. CUPS sends jobs to the printer at a rate of less than
100kB/sec.

In contrast to this, throwing data into the appropriate port, or indeed
printing from a Windows machine results in performance approaching
850kB/sec to the very same device. For printing large jobs (such as a
600DPI full page), this makes a vast time difference.

The printer in question is an HP LaserJet 4 Plus with Postscript module
(being used as a PS rather than a PCL/PJL printer, and I can verify that
CUPS is not trying to convert the incoming PS before sending it) at 34MB
RAM. The JetDirect card is J2552-60013, which unfortunately does not
natively support IPP, even with the latest firmware.

I'd be happy to provide any required additional information, let me know
if I've missed out something important.

-Dave.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux jesmos 2.4.21 #3 SMP Wed Oct 8 15:14:32 BST 2003 i686
Locale: LANG=en_GB, LC_CTYPE=en_GB

Versions of packages cupsys depends on:
ii  adduser                  3.51            Add and remove users and groups
ii  debconf                  1.3.15          Debian configuration management sy
ii  gs-esp                   7.05.6-2.1      The Ghostscript Postscript interpr
ii  libc6                    2.3.2-9         GNU C Library: Shared libraries an
ii  libcupsimage2            1.1.19final-1.4 Common UNIX Printing System(tm) - 
ii  libcupsys2               1.1.19final-1.4 Common UNIX Printing System(tm) - 
ii  libgcc1                  1:3.3.2-1       GCC support library
ii  libgnutls7               0.8.9-2         GNU TLS library - runtime library
ii  libpam0g                 0.76-14         Pluggable Authentication Modules l
ii  libpaper1                1.1.13          Library for handling paper charact
ii  libslp1                  1.0.11-4        OpenSLP libraries
ii  libstdc++5               1:3.3.2-1       The GNU Standard C++ Library v3
ii  zlib1g                   1:1.1.4-16      compression library - runtime

-- debconf information:
* cupsys/raw-print: true
* cupsys/lpr-backend-setuid: false



--- End Message ---
--- Begin Message ---
On 7/15/07, dh@winterwolf.co.uk <dh@winterwolf.co.uk> wrote:
Package: cupsys
Version: 1.2.11-3
Followup-For: Bug #218910


Martin-Éric,

Thanks for getting in touch. I can confirm that the bug does still
apply with this version of CUPS, but it might not be the fault of CUPS -
it could be the fault of the version of the JetDirect card I have in my
printer. Unfortunately, I have no way at present to try sending data
using anyhting other than cups to the LDP running on the card.

If I was looking at the situation now, I probably wouldn't have
reported the bug, as there's no clear evidence that CUPS is to blame
here. Coupled with that fact that running it's easy to work around the
problem by sending data to a raw port, I'd be quite happy if this bug
were closed.

Then seeing as it doesn't report a broken feature and how speed is a
subjective perception, I'll simply close it. Thanks for having taken
the time to reply.

--
Martin-Éric Racine
http://q-funk.iki.fi

--- End Message ---

Reply to: