Did you kill the old instance of cups-browsed, which was stuck on 200% CPU, with
``` killall -9 cups-browsed ``` before doing the update? If not, the update can take significantly longer. This is due to the fact that on regular restarting of cups-browsed only the SIGTERM signal (`kill -TERM`) is used, and this does not stop the stuck cups-browsed. Therefore, after a certain timeout period with the cups-browsed process not disappearing a SIGKILL is sent (`kill -9`). To make sure that your updated cups-browsed is actually not getting stuck any more, please follow the "[ Test Plan ]" procedure in the description at the top of 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
