Comment 5 for bug 879172

Unfortunately, I still see this bug in 2.6.1-6.

I experience the same problem, although I have not changed the output directory (so it's still at its default ~/PDF) and the proposed lines in /etc/apparmor.d/usr.sbin.cupsd are set as suggested above.

I don't see how the bug could have been fixed if the core of the problem has not been addressed at all. The debug logs above show clearly that the output file is deleted immediately after creation. My debug logs are exactly the same. So what has apparmor to do with that? Apparmor would _prevent_ the creation of the file. But what's the point of _deleting_ the file after creation? Is there any point in using cups-pdf if you would not want to _keep_ the generated file?