Bug#497492: [Pkg-cups-devel] Bug#497492: Child exited on signal 13!

Martin Pitt wrote: It does, since the crash happens due to a SIGPIPE, when a cups subprocess without stderr tries to write this warning to stderr. Yes, your right. I obviously didn't read the strace output properly... Just to make sure, is there any runtime config option to disable this

Bug#497492: [Pkg-cups-devel] Bug#497492: Child exited on signal 13!

Hi Brian, Brian May [2008-09-07 19:12 +1000]: Thanks. Will try it ASAP. Probably tomorrow, my time zone. Great! You'll test the current experimental version? Assuming this works, do you think there is any chance of it getting into Lenny? Yes, I very much think so. The current unstable

Bug#497492: [Pkg-cups-devel] Bug#497492: Child exited on signal 13!

Martin Pitt wrote: Yes, I very much think so. The current unstable version has approval and should go to testing RSN, after that I'll upload another one. So far so good... I saw the error Child exited on signal 13! in the print queue, but then realized that was because I used your email as

Bug#497492: [Pkg-cups-devel] Bug#497492: Child exited on signal 13!

tag 497492 -moreinfo tag 497492 upstream confirmed thanks Hi Brian, Brian May [2008-09-05 11:32 +1000]: What Steve Cotton said, while interesting, I suspect this shows that the message is not related to my crashes. It does, since the crash happens due to a SIGPIPE, when a cups subprocess