Description of problem: It appears that network discovered printers are never removed any more, either when moving off network or when the printer is removed from the sharing host. This causes problems with applications trying to contact non-existent hosts. Version-Release number of selected component (if applicable): cups-1.7.5-13.fc21.x86_64 For example, the following printer in /etc/cups/printers.conf no longer exists: <Printer frost> UUID urn:uuid:abef690e-08e4-3bd8-519f-5af296ae1d55 Info HP LaserJet 5m in Computer Room Location 10.10.10.1 DeviceURI ipp://10.10.10.1:631/printers/frost State Idle StateTime 1422889225 Type 6 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Option cups-browsed true </Printer> and is no longer advertised on the network.
Running cups-browsed in debug mode - it seems that cups_handle_queues is never called, so that printers are never removed. Printer added: cups-browsed: listening cups-browsed: browse packet received from 10.10.10.1 cups-browsed: browsed queue name is test cups-browsed: Found CUPS queue: test on host 10.10.10.1. cups-browsed: Bonjour IDs: Service name: "Generic text-only printer", Service type: "", Domain: "" cups-browsed: checking queues in 0s cups-browsed: Processing printer list ... cups-browsed: Creating/Updating CUPS queue for test cups-browsed: listening But then we are stuck in listening. The handle_cups_queues() timeout appears to have be set to zero to get processed immediately, but is never set again.
Filed upstream.
Fixed upstream.
This was fixed in cups-filters-1.0.65.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.