[cups] duplex not working ("Transport endpoint is not connected")
Martin Vogt
martin.vogt at itwm.fraunhofer.de
Fri Feb 5 04:34:53 PST 2016
Hello,
I debugged it a bit. I'm using cups 1.6.4.
When I change the following:
--- cups-1.6.4/cups/util.c 2013-07-23 14:31:34.000000000 +0200
+++ cups-1.6.4.new/cups/util.c 2016-02-05 13:27:30.961231224 +0100
@@ -1707,7 +1707,7 @@
{
const char *device_uri = NULL; /* device-uri value */
- if ((attr = ippFindAttribute(response, "device-uri",
+ if ((attr = ippFindAttribute(response, "Xevice-uri",
IPP_TAG_URI)) != NULL)
device_uri = attr->values[0].string.text;
The command lpoptions -p cpsg0a -l works.
Thus 1.3.9 server sends the device-uri and this is used by the 1.6.4
client in "version=1.1" mode.
But the IP for this device not accessible from the client and cannot
connect to the printer directly.
best regards,
Martin
On 19.01.2016 12:15, Martin Vogt wrote:
> I try to use duplex printing from my workstations (RHEL7)
> which access a 1.3.9 cups server (SLE11-SP4)
>
> Basic printing works on RHEL7, but nothing more, for
> example download the .ppd.
>
> On RHEL7 (cups 1.6) I get the following error:
>
>> vogt at pxe1[~]>lpoptions -p cpsg0a -l
>> lpoptions: Unable to get PPD file for cpsG0a:
>> Transport endpoint is not connected
>
> With a cups 1.3 client this works:
>
>> vogt at sle11[~]>lpoptions -p cpsg0a -l | wc -l
>> 53
>
More information about the cups
mailing list