I cannot reproduce this bug.
Do you have avahi-daemon running? Does avahi-daemon take 100% CPU?
Please run the command
cupsctl LogLevel=debug2
and try to reproduce the problem. As soon as it occurs again, attach your error_log to this bug report.
See "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems for how to handle your error_log.
If the avahi-daemon is not running, start it ("sudo start avahi-daemon"). Does the problem go away then?
If the avahi-daemon takes 100% CPU, restart it ("sudo stop avahi-daemon; sudo start avahi-daemon"). Does the problem go away then?
I cannot reproduce this bug.
Do you have avahi-daemon running? Does avahi-daemon take 100% CPU?
Please run the command
cupsctl LogLevel=debug2
and try to reproduce the problem. As soon as it occurs again, attach your error_log to this bug report.
See "CUPS error_log" on https:/ /wiki.ubuntu. com/DebuggingPr intingProblems for how to handle your error_log.
If the avahi-daemon is not running, start it ("sudo start avahi-daemon"). Does the problem go away then?
If the avahi-daemon takes 100% CPU, restart it ("sudo stop avahi-daemon; sudo start avahi-daemon"). Does the problem go away then?