Bug 1311387 - Can't connect to network cups printer when both cups and dnssd are enabled
Can't connect to network cups printer when both cups and dnssd are enabled
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Zdenek Dohnal
Fedora Extras Quality Assurance
Depends On: 1323042
  Show dependency treegraph
Reported: 2016-02-24 02:03 EST by Jonathan Dieter
Modified: 2016-12-20 13:59 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 13:59:10 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
filtered cups debug log (7.69 KB, text/plain)
2016-02-24 02:05 EST, Jonathan Dieter
no flags Details

  None (edit)
Description Jonathan Dieter 2016-02-24 02:03:57 EST
Description of problem:
We have a print server running fully updated Fedora 23 that is configured to share its printers using both the cups protocol and the dnssd protocol.  When our Fedora 23 workstations are started, they can initially print, but after a minute or two, printing stops working, and the cups log (set at debug) says "Unknown URI scheme".

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Set up print server and connect printer
2. Set "BrowseLocalProtocols dnssd cups" in /etc/cups/cups-browsed.conf
3. Boot workstation and wait five minutes
4. Attempt to print to network printer

Actual results:
Unable to print

Expected results:
Job prints
Comment 1 Jonathan Dieter 2016-02-24 02:05 EST
Created attachment 1130060 [details]
filtered cups debug log
Comment 2 Jonathan Dieter 2016-02-24 02:07:15 EST
We've upgraded all of our systems to Fedora 23, so my current workaround is to just disable the cups protocol on the server and only use dnssd.  This fixes the problem for us, but obviously doesn't help if someone's using a more mixed environment.
Comment 3 Fedora Admin XMLRPC Client 2016-06-24 06:30:34 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 4 Fedora End Of Life 2016-11-24 10:44:18 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2016-12-20 13:59:10 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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