I tried to make a patch to solve the issue, but I got stuck. I wrote an email to the upstream author of cups-pdf Volker C. Behr. He pointed out some issue: and after checking his suggestions, it seems that one of his hunch is the winner: it is AppArmor. Try:
1. Delete the PDF directory, then try to print. Won't work, as mentioned above.
2. Stop AppArmor (sudo /etc/init.d/apparmor stop), and try to print again. PDF directory gets created, and everything is fine.
I have no clue what it is in AppArmor config, that causes this (I have very little knowledge of AppArmor), so this is beyond me. I guess this is an AppArmor bug.
P.S.: Just for the record, Volker C. Behr replied in 20 minutes after I wrote the mail to him. So cheers and thanks to him from here too.
I tried to make a patch to solve the issue, but I got stuck. I wrote an email to the upstream author of cups-pdf Volker C. Behr. He pointed out some issue: and after checking his suggestions, it seems that one of his hunch is the winner: it is AppArmor. Try: d/apparmor stop), and try to print again. PDF directory gets created, and everything is fine.
1. Delete the PDF directory, then try to print. Won't work, as mentioned above.
2. Stop AppArmor (sudo /etc/init.
I have no clue what it is in AppArmor config, that causes this (I have very little knowledge of AppArmor), so this is beyond me. I guess this is an AppArmor bug.
P.S.: Just for the record, Volker C. Behr replied in 20 minutes after I wrote the mail to him. So cheers and thanks to him from here too.
Rgds,
Attila