CUPS server error: 'Transport endpoint is not connected'.

Asked by SuffolkPunch on 2019-05-17

I have 2 PCs on my home LAN both running Linux Mint 18.3 64-bit Cinnamon:
LAN
|
|---PC1
|
|--PC2--local printers

PC1 uses cups to print to PC2 which has 2 usb local printers, . Both PCs had CUPS v 2.1.3-4ubuntu0.7 installed.

After updating cups on both PCs to 2.1.3-4ubuntu0.8, PC1 could no longer print to PC2. Instead, when I try to print a test page PC1 popped-up the following errors messages

    "CUPS server error: There was an error during the CUPS operation: 'Transport endpoint is not connected'."
    "Raw queue: Unable to get queue details. Treating queue as raw."

As a fix I used TimeShift to revert back to cups v 2.1.3-4ubuntu0.7 on both PCs. And everything then worked fine.

Is this a known bug? How do I figure-out what's causing this?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu cups Edit question
Assignee:
No assignee Edit question
Last query:
2019-05-17
Last reply:
2019-05-17
Manfred Hampl (m-hampl) said : #1

Manfred Hampl suggests this article as an answer to your question:
FAQ #3041: “No support for Linux Mint”.

SuffolkPunch (mjw-z) said : #2

Thanks Manfred.

Can you answer a non Linux Mint question: what changed between cups 2.1.3-4ubuntu0.7 and 2.1.3-4ubuntu0.8?

It looks like there was just a single change:
cups (2.1.3-4ubuntu0.8) xenial; urgency=medium

  * d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
    installed (LP: #1822062)

 -- Victor Tapia <email address hidden> Tue, 23 Apr 2019 17:44:19 +0200

Is that correct?

Martin

Can you help with this problem?

Provide an answer of your own, or ask SuffolkPunch for more information if necessary.

To post a message you must log in.