I extracted the patch and will upload a dapper update. Does anyone have a monkey-proof recipe how to trigger this condition?
** Description changed: - Hello! - + Impact: Occasionally, I notice that a process "gnome-cups-icon" eats 100% CPU. Upon a "sudo killall -TERM gnome-cups-icon", it restarts and does no longer eat CPU. - This might be related to the issue described in #43352, but I do not - have any pending print jobs in the queue like described in this bug - report. + Problem: When calling ippRead() in client programs, it sometimes returns + IPP_IDLE which was not actually meant to get passed to outside. Thus it + got handled as an error condition and the program logic got caught in a + busy loop. Instead - Regards, + Solution: + This was fixed upstream in http://www.cups.org/str.php?L2179 in cups 1.2.11 in February. One half of the patch was backported to Edgy's 1.2.4, and we did not get further complaints since then. The second half got shipped in gutsy, and apparently is not needed to fix the most common cases, but it has not shown any regressions for 9 months, so it should be applied, too. - Martin + Unfortunately there does not seem to be a reliable test case how to + trigger this behaviour. Seems we should rely on bug reporter feedback. ** Changed in: cupsys (Ubuntu Dapper) Assignee: (unassigned) => Martin Pitt (pitti) Status: Confirmed => In Progress -- gnome-cups-icon uses 100% CPU https://bugs.launchpad.net/bugs/44196 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
