Thanks everyone for posting logs here. I would like to have another thing from everyone who runs into the problem.
1. When you observe the problem, DO NOT kill cups-browsed. 2. Save the debug log and attach it to this bug report. 3. Determine the process ID (PID) of cup-browsed: ps aux | grep cups-browsed | grep -v grep cups-browsed 846190 0.0 0.0 112932 5760 ? Ssl 00:00 0:00 /usr/sbin/cups-browsed The first number (second word) in the line is the PID 4. Install the debug symbols package of cups-browsed. Its name is "cups- browsed-dbgsym". Follow the instructions on https://ubuntu.com/server/docs/debug-symbol-packages 5. Install the debugger gdb if needed: sudo apt install gdb 6. Attach the debugger gdb to cup-browsed: sudo gdb attach PID or sudo -u cups-browsed attach PID Replace PID by the PID you determined in (3) On the prompt of the debugger enter the command t a a bt You get some output. If it ends with --Type <RET> for more, q to quit, c to continue without paging-- press Enter, until you get back to the prompt: (gdb) DO NOT press Enter when you are at the prompt. Now copy the complete output of gdb into an editor, save the file and attach it to this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049315 Title: cups-browsed running non-stop on two cores To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
