Ubuntu
cups-browsed package

  1. Bug #2018504
  2. Comment #12

Comment 12 for bug 2018504

Revision history for this message
Marius Gedminas (mgedmin) wrote :

Today I noticed cups-browsed eating 100% CPU for a while (about 20 minutes). I restarted it with 'sudo service cups-browsed restart', which took 1 minute 36 seconds (presumably cups-browsed didn't want to be restarted so systemd killed it forcefully after a 1m30s timeout?).

I have

    DebugLogging file stderr

in my /etc/cups/cups-browsed.conf from a previous debugging attempts (for a different problem). /var/log/cups-browsed/cups-browsed_log contains messages from after the restart (with no CPU eating problems), so here's /var/log/cups-browsed/cups-browsed_previous_logs. The relevant time interval is from Fri May 19 09:04:15 2023, when I resumed my laptop in the office, until the end.

It doesn't look very informative to me: a bunch of HTTP timeouts, an EINVAL, a IPP-Cancel-Subscription (whatever that means), and then complete silence until it gets a SIGTERM.