I've verified that 0.9.2 fixes the 100 CPU issue. (for those who can't wait the merge into lucid, use the ppa:cr3/ppa repository)
But I wonder if the fix isn't just a workaround of a gksu problem. Because ggksu doesn't seem to handle signals properly. I.e. killing the gksu process doesn't kill the children. For example If I do this: mkdir -p /tmp/checkboxMsblJo touch /tmp/checkboxMsblJo/input touch /tmp/checkboxMsblJo/output gksu -k -- PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games /usr/share/checkbox/backend /tmp/checkboxMsblJo/input /tmp/checkboxMsblJo/output and kill the gksu process (e.g. CTRL-C), I will still have a 100% CPU process running. So the fix works, but only because it destroys the pipe that backend is waiting on. Should a bug be opened against gksu ? -- Backend does not get terminated https://bugs.launchpad.net/bugs/553328 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
