I'm running Ubuntu 23.04 in a university environment with several printers on the local network. This morning I performed the following steps:
1. I stopped cups-browsed.
2. I edited the configuration file to have "DebugLogging file" and "DebugLogFileSize 0".
3. I started cups-browsed. It created a log file /var/log/cups-browsed/cups-browsed_log, and did not appear to be using an usual amount of CPU.
4. I unplugged the network cable from my laptop, then plugged it back in. Immediately cups-browsed started using 100% CPU. It appears that at the same time, the previous log file was renamed to cups-browsed_previous_logs, and a new log file cups-browsed_log was created.
5. I let cups-browsed run with 100% CPU for a couple of minutes. It didn't seem to write a huge amount of log output.
6. I stopped cups-browsed.
I'll attach both cups-browsed_log and cups-browsed_previous_logs.
I'm running Ubuntu 23.04 in a university environment with several printers on the local network. This morning I performed the following steps:
1. I stopped cups-browsed. cups-browsed/ cups-browsed_ log, and did not appear to be using an usual amount of CPU. previous_ logs, and a new log file cups-browsed_log was created.
2. I edited the configuration file to have "DebugLogging file" and "DebugLogFileSize 0".
3. I started cups-browsed. It created a log file /var/log/
4. I unplugged the network cable from my laptop, then plugged it back in. Immediately cups-browsed started using 100% CPU. It appears that at the same time, the previous log file was renamed to cups-browsed_
5. I let cups-browsed run with 100% CPU for a couple of minutes. It didn't seem to write a huge amount of log output.
6. I stopped cups-browsed.
I'll attach both cups-browsed_log and cups-browsed_ previous_ logs.