I'm pretty sure that it's not a bug in cups-pdf but a bug in the AppArmor configuration for cups-pdf.
Workaround (and proof that it's an AppArmor configuration issue):
open the file /etc/apparmor.d/usr.sbin.cupsd
and edit the line:
/usr/lib/cups/backend/cups-pdf {
in order to get:
/usr/lib/cups/backend/cups-pdf flags=(complain) {
restart AppArmor with 'sudo /etc/init.d/apparmor restart'
CUPS-PDF works again, QED!
As far as I understand it, the workaround removes the protection around cups-pdf, someone with more knowledge can probably fix the config file in a more sensitive manner.
As the file /etc/apparmor.d/usr.sbin.cupsd comes with the 'cups' package, this bug should be reassigned.
I'm pretty sure that it's not a bug in cups-pdf but a bug in the AppArmor configuration for cups-pdf.
Workaround (and proof that it's an AppArmor configuration issue):
open the file /etc/apparmor. d/usr.sbin. cupsd
and edit the line: lib/cups/ backend/ cups-pdf { lib/cups/ backend/ cups-pdf flags=(complain) {
/usr/
in order to get:
/usr/
restart AppArmor with 'sudo /etc/init. d/apparmor restart'
CUPS-PDF works again, QED!
As far as I understand it, the workaround removes the protection around cups-pdf, someone with more knowledge can probably fix the config file in a more sensitive manner.
As the file /etc/apparmor. d/usr.sbin. cupsd comes with the 'cups' package, this bug should be reassigned.
Hope this helps, Eric