These processes
-----
$ ps aux | grep cups-browsed | grep -v grep
root 2912 0.0 0.0 2892 1708 ? Ss 10:13 0:00 /bin/sh
/snap/cups/1047/scripts/run-cups-browsed
root 3407 0.0 0.0 2892 892 ? S 10:13 0:00 /bin/sh
/snap/cups/1047/scripts/run-cups-browsed
-----
come from the CUPS Snap. They are from a wrapper script to start cups-browsed,
but in your case the CUPS Snap does not start cups-browsed, as you have a
classically installed CUPS and the CUPS Snap is only running as proxy for
snapped applications. There is no ยจ../cups-browsed" process, so cups-browsed is
currently not running for you.
You have attached gdb to cupsd.
The instructions I have posted are for applying when cups-browsed is
running and stuck, not after killing it. They only make sense if there
are actually 1 or 2 cups-browsed processes hanging in a 100%-CPU busy
loop.
For your patch on CUPS, which Michael has actually accepted, I am not
absolutely sure whether it will solve the problem. If you do not add the
"return(NULL);" line, the flow will go into the "return(NULL);" right
after the "if () {} else if {}" and so we have no different effect. Or
is this not the case?
--
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
