gnome-cups-icon uses 100% CPU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-cups-manager |
Unknown
|
Medium
|
|||
cupsys (Debian) |
Fix Released
|
Unknown
|
|||
cupsys (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Dapper |
Fix Released
|
Medium
|
Martin Pitt | ||
gnome-cups-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
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.
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
Solution:
This was fixed upstream in http://
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 gnome-cups-manager: | |
status: | Needs Info → Confirmed |
Changed in gnome-cups-manager: | |
status: | Unknown → Unconfirmed |
Changed in gnome-cups-manager: | |
status: | Unknown → Unconfirmed |
Changed in gnome-cups-manager: | |
status: | Unconfirmed → Confirmed |
Changed in gnome-cups-manager: | |
status: | Confirmed → Fix Released |
Changed in gnome-cups-manager: | |
status: | Unconfirmed → Rejected |
Changed in cupsys: | |
status: | In Progress → Fix Committed |
Changed in gnome-cups-manager: | |
status: | Unconfirmed → Rejected |
Changed in gnome-cups-manager: | |
importance: | Unknown → Medium |
status: | Invalid → Unknown |
Hi Martin,
The next time gnome-cups-icon eats up 100% CPU, could you run
the following command which should log what the process is trying
to do?
$ strace -Ff -p $(pidof gnome-cups-icon) 2>&1 | tee /tmp/strace.log
After about ten seconds of stuff scrolling up your screen, you can
hit Control-C to stop strace.
Then, please attach /tmp/strace.log to this bug report: /launchpad. net/distros/ ubuntu/ +bug/44196/ +addattachment
https:/
Thanks.