Bug 1087052 - Cannot connect to my Samsung laser printer: cups destination not connected
Summary: Cannot connect to my Samsung laser printer: cups destination not connected
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-13 13:26 UTC by antonio montagnani
Modified: 2015-02-12 17:14 UTC (History)
4 users (show)

Fixed In Version: system-config-printer-1.4.6-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-12 17:14:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
debug file -troubleshooter (63.67 KB, text/plain)
2014-04-13 21:22 UTC, antonio montagnani
no flags Details
system-config-printer debug file (3.44 KB, text/plain)
2014-04-15 11:27 UTC, antonio montagnani
no flags Details
system-config-printer -debug printer when adding a queue (5.30 KB, text/plain)
2014-04-15 17:03 UTC, antonio montagnani
no flags Details
debug during manually adding a queue (12.05 KB, text/plain)
2014-04-16 16:35 UTC, antonio montagnani
no flags Details

Description antonio montagnani 2014-04-13 13:26:49 UTC
Description of problem:
I cannot use my remote Samsung Laser at home

Version-Release number of selected component (if applicable):
cups-1.7.1-8.fc20.x86_64

How reproducible:
always

Steps to Reproduce:
1.try to discover and install on my laptop a printer that is connected to my desktop
2.printer is not autodiscovered, i.e. it should be in the list automatically
3.when printer is discovered as a network printer in the selection list it it searched as remote CUPS printer connected via DNS-SD, but when I apply I get CUPS server error: destination socket is not connected

Actual results:
no installation of remote printer

Expected results:
installation of remote printer (it was working on F-19)

Additional info:
printer is fine when used locally

Comment 1 antonio montagnani 2014-04-13 15:30:19 UTC
the correct message is: 
CUPS server error
There was an error during the CUPS operation: 'Il socket di destinazione non รจ connesso'. (destination socket not connected)

Comment 2 antonio montagnani 2014-04-13 16:03:33 UTC
lpinfo -v
network http
network lpd
network ipps
serial serial:/dev/ttyS0?baud=115200
network socket
network https
network beh
network ipp
direct usb://Samsung/ML-1610?serial=3921BRJL304582..
network smb

Comment 3 antonio montagnani 2014-04-13 16:22:52 UTC
On the remote laptop (Aficio printers are work network printers and work fine)

# Printer configuration file for CUPS v1.7.1
# Written by cupsd on 2014-04-13 18:20
# DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
<Printer CUPS-PDF-Printer>
UUID urn:uuid:6cb120b8-852c-3898-4b0d-8057b68900b4
Info CUPS-PDF
MakeModel Generic CUPS-PDF Printer
DeviceURI cups-pdf:/
State Idle
StateTime 1397393994
Type 8450124
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
Option media iso-a4
</Printer>
<Printer printer>
UUID urn:uuid:7f1b74b2-5556-38ad-6f28-c6f7bb6b1f25
Info 
Location 
DeviceURI dnssd://Samsung%20ML-1610%20%40%20pcdesktop1._ipp._tcp.local/cups
State Idle
StateTime 1397405981
Type 6
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
</Printer>
<DefaultPrinter Ricoh-Aficio-MP-C3002>
UUID urn:uuid:cd5b686d-0cd3-3799-78f6-ce46396a02ac
Info Ricoh Aficio MP C3002
Location 10.0.0.60
MakeModel Ricoh Aficio MP C3002 PXL
DeviceURI socket://10.0.0.60:9100
State Idle
StateTime 1397229873
Reason waste-receptacle-full-warning
Type 8401148
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
Attribute marker-colors \#000000,none,#00FFFF,#FF00FF,#FFFF00
Attribute marker-levels 20,0,90,100,100
Attribute marker-names Toner Nero,Toner di scarto,Toner Ciano,Toner Magenta,Toner Giallo
Attribute marker-types toner,waste-toner,toner,toner,toner
Attribute marker-change-time 1397229873
</Printer>
<Printer RICOH-Aficio-MP-W2401>
UUID urn:uuid:e01837eb-031b-3e46-4175-8aa85b2bd5cd
Info RICOH Aficio MP W2401
MakeModel Ricoh Aficio MP W2401 PS
DeviceURI dnssd://RICOH%20Aficio%20MP%20W2401%20%5B5691E3%5D._pdl-datastream._tcp.local/
State Idle
StateTime 1395234605
Type 8450244
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
Attribute marker-colors \#000000,#000000
Attribute marker-levels -1,-1
Attribute marker-names Toner,Toner di scarto
Attribute marker-types toner,waste-toner
Attribute marker-change-time 1395234605
</Printer>

Comment 4 antonio montagnani 2014-04-13 21:22:44 UTC
Created attachment 885947 [details]
debug file -troubleshooter

funny, as I could install the printer by using cups admin tool, and printer was discovered fine.But I had no success in printing test file, see attachment. Anyway I still get same error if I delete/reinstall printer in system-config-printer

Comment 5 Tim Waugh 2014-04-14 13:34:04 UTC
(In reply to antonio montagnani from comment #0)
> 1.try to discover and install on my laptop a printer that is connected to my
> desktop
> 2.printer is not autodiscovered, i.e. it should be in the list automatically

Here's what I understand by the above: you've started an application, let's stay gedit or something, and selected File->Print, but the printer is not in the list of printers in the Print dialog.

Have I understood correctly?

> 3.when printer is discovered as a network printer in the selection list it
> it searched as remote CUPS printer connected via DNS-SD, but when I apply I
> get CUPS server error: destination socket is not connected

Can you explain what you are doing in this step? What application do you start, which buttons do you press, etc?

Comment 6 antonio montagnani 2014-04-14 14:52:13 UTC
No, I mean that I assume that also on the remote computer I should see the printer in the available printer list,it doesn't happen maybe due to  the type of printer.

Then I tried to add a printer with system-config-printer,printer is discovered attached to 192.168.1.3 that is the correct IP of the computer where printer is connected.

Then I get the error of destination socket not connected...

Then I disisnstalled the printer on the remote computer then I tried to reinstall by CUPS administration tool,printer was discovered and installed, but no way of printing, it says that is not connected!!!

Firewalld is in home zone on both computer (anyway it was working as a charm in F19): only difference is that I am using a new laptop with a fresh F20, while on the desktop I am using a F20 updated from F19.

Comment 7 Tim Waugh 2014-04-14 15:06:38 UTC
(In reply to antonio montagnani from comment #6)
> No, I mean that I assume that also on the remote computer I should see the
> printer in the available printer list,it doesn't happen maybe due to  the
> type of printer.

Can you explain what you mean by "the available printer list" in terms of what actions you perform, and what results you expect? Please be precise -- it really helps when trying to narrow down this sort of problem.

Comment 8 antonio montagnani 2014-04-14 15:11:14 UTC
I assume (but I am not sure) that also on the remote computer I should see the printer in system-config-printer tool (the icon of the available printer).
That in my case is not true

I am using 1.4.4 system-config-printer

Comment 9 Tim Waugh 2014-04-15 08:56:59 UTC
Ah, no, it won't show up there. This is a change from how things used to work.

Previously, cupsd would keep track of discovered print queues on the network. Now, however, applications discover network print queues when presenting the 'Print' dialog. A notable exception is that Firefox won't do this currently, owing to the fact that it still uses gtk2 and not gtk3 yet.

Perhaps you could verify that e.g. gedit's print dialog shows the printer?

On to the other part: the error from cups, shown by system-config-printer. Could you please run 'system-config-printer --debug &>output' and attach the output? Thanks.

Comment 10 antonio montagnani 2014-04-15 11:27:24 UTC
Created attachment 886448 [details]
system-config-printer debug file

printer is not available on gedit printer list

Attached the debug file for system-config-printer

Comment 11 Tim Waugh 2014-04-15 13:52:54 UTC
Did you try adding a queue during that run of system-config-printer? It just looks like it started and then was closed.

Comment 12 antonio montagnani 2014-04-15 16:23:57 UTC
not clear to me what is the meaning of adding a queue...if i cannot see the printer in the list.
What am I missing?

Comment 13 antonio montagnani 2014-04-15 17:03:56 UTC
Created attachment 886556 [details]
system-config-printer -debug printer when adding a queue

Hope that adding a queue means try to add the printer from system-config-printer

Comment 14 Tim Waugh 2014-04-16 11:23:43 UTC
I'm trying to diagnose step 3 of your original 'how to reproduce' instructions. Were you not using system-config-printer to do that?

Comment 15 antonio montagnani 2014-04-16 11:41:54 UTC
I was using system-config-printer as it was not discovered automatically (I am sure that I could print from remote computer in F19, F18 and previous releases)

So I opened system-config-printer, I got the printer in Network printers (that was correctly shown as connected to my desktop only by IP) and I added it there.Then I got the error in socket connection.

Hope it can help

Comment 16 Tim Waugh 2014-04-16 16:23:29 UTC
So, can you do what you were doing in step 3, but using the --debug parameter to system-config-printer?

Comment 17 antonio montagnani 2014-04-16 16:35:53 UTC
Created attachment 886935 [details]
debug during manually adding a queue

this is the full listing, at the end I got the usual message of Cups socket disconnected

Comment 18 antonio montagnani 2014-04-23 17:26:31 UTC
no improvement also with cups from updates-testing

Comment 19 antonio montagnani 2014-04-26 16:08:13 UTC
I made a test, I disabled the share option on the printer, and also I disabled the option to publish shared printers on the network.
Then I re-enabled both options and I was asked to allow adjustment of firewall rules!!! now everything works, not clear why operator is asked twice for root password anytime he wants to apply any change.Furthermore,it is not clear why in Centos I can print any document on the shared printer but test page print is greyed in system-config-printer

Comment 20 antonio montagnani 2014-04-28 13:04:57 UTC
an additional comment: I am not sure that in the meantime I changed the default zone in firewalld, but I suppose that any adjustment should follow any change.

Comment 21 Tim Waugh 2014-06-25 10:29:10 UTC
(In reply to antonio montagnani from comment #19)
> now everything works, not clear why operator is asked
> twice for root password anytime he wants to apply any change.

This is because of the way PolicyKit works: access is granted on a fine-grained basis. There is an open bug tracking changing this: bug #714820.

> Furthermore,it
> is not clear why in Centos I can print any document on the shared printer
> but test page print is greyed in system-config-printer

It gets greyed out if the queue doesn't accept PostScript, or is not enabled, or is rejecting jobs.

Comment 22 Tim Waugh 2014-07-16 12:45:42 UTC
I think the cause of this is that the printer is discoverable but its PPD cannot be fetched.

I've fixed this upstream in commit 755a800.

Comment 23 John Duchek 2015-02-12 05:07:29 UTC
I am having similar problems with my Samsung CLP-310 under fedora 21.  Used to work.  The computer sees it, installs it (using a CLP-350 driver; it used to use the 310, but it is no longer listed.) When I try to print a test page, the printer lights blinks for a bit, then nothing.  The computer says it sent the test page, and it is now idle.

It really sucks since it used to work fine.

john

Comment 24 antonio montagnani 2015-02-12 05:38:35 UTC
if you refer to a shared printer, you have to enable ipp and ipp-client on the computer sharing the printer

Comment 25 Tim Waugh 2015-02-12 17:14:17 UTC
Closing this as the fix went into 1.4.6 (FEDORA-2014-13184).

John: your problem sounds different to this one. Please file a separate report.


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