OK -- Here goes: Freeing up space after cups starts using excessive CPU allows it to work properly (It receives a SIGPIPE though when run under gdb). Here's the backtrace at the point where it was using CPU:
backtrace: #0 0xffffe410 in __kernel_vsyscall () #1 0xb7e994c3 in __write_nocancel () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7eb117e in cupsFileGetChar () from /usr/lib/libcups.so.2 #3 0xb7eb1735 in cupsFileFlush () from /usr/lib/libcups.so.2 #4 0x0807e658 in ?? () #5 0x080eb5b0 in ?? () #6 0x0809634c in _IO_stdin_used () #7 0x080e0bc0 in ?? () #8 0x0809693a in _IO_stdin_used () #9 0x08099400 in Sleeping () #10 0x0808c832 in _IO_stdin_used () #11 0x080e3bba in ?? () #12 0x00000001 in ?? () #13 0x00000001 in ?? () #14 0x000000c8 in ?? () #15 0x00000000 in ?? () -- 100% CPU when disk is full https://launchpad.net/bugs/66612 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
