[cups-devel] [UNKN] STR #4620: Superflous printer errors in appsocket 9100 and ipp 631, works in lpr/lpd 515
noreply at cups.org
Tue Apr 21 21:49:06 PDT 2015
-----BEGIN PGP SIGNED MESSAGE-----
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
Arch Linux: 3.19.3-3-ARCH x86_64
cups 2.0.2-4, cups-filters 1.0.68-1, cups-pdf 2.6.1-2, libcups 2.0.2-4
hplip installed then removed
foomatic installed then removed
gutenprint installed then removed
Printers: HP LaserJet Pro 400 m401n, Lexmark T640, HP P2035 with JetDirect
170x, Okidata Oki B411dn
echo -e "\f" > x; lp -dPrinter x; rm x
This works especially good with my Oki B411 because it is programmed to not
print blank pages.
If I set up a printer with appsocket or ipp I see in the cups web
Idle - "Waiting for printer to finish." (appsocket)
Idle - "Waiting for job to complete." (ipp)
and netstat -an reports a connection to the printer which takes a minute or
so to disappear.
If I tell cups to disconnect with "socket://0.0.0.0:9100/?waiteof=false", I
Idle - "Connected to printer."
Except that cups is lying. If I'm fast I can see a connection in netstat
- -an for about 10 seconds.
If I use lpr I get:
Idle - "Data file sent successfully."
That sounds like what I'm looking for. netstat -an shows a connection for
about 10 seconds. I'd rather not use lpr for every printer. It's harder to
set up and only some printer manufacturers are forthcoming with their queue
names and function and the big IBM list doesn't have all brands. I don't
like strange printing problems because of strange queue names.
Some have suggested that the printers are failing to close the appsocket.
Maybe they are but all brands are doing it and they can't all be broken. I
think it's a cups problem and there are two problems.
* cups is not updating the web display correctly. Each connection type is
pulling from a grab bag of random messages that hang around and scare
people into thinking that their test servers will break in production when
multiple servers start hitting the printers.
* appsocket is not expiring sockets in the same timely fashion that other
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: GPGTools - https://gpgtools.org
-----END PGP SIGNATURE-----
More information about the cups