Bug#852436: cups-browsed uses 100% CPU
Thank you for the log file.
The high load was probably caused by cups-browsed repeatedly creating
local queues for the discovered remote queues as it did not recognize
that the queues were already successfully generated.
I have corrected the error checking now to interpret the resulting IPP
status codes correctly as success or error. This I have done on the
upstream BZR repository, rev. 7601.
The lines in the log file leading to this assumptions are:
Tue Jan 24 14:49:52 2017 Unable to create/modify CUPS queue (Success)!
which appear several times. cups-browsed considered the operation having
errored, therefore outputting this line. In the parantheses the last
error string of the operating system is inserted, which is "Success"
meaning that the system did not see any error here.