Changing the recommendation to a PCL driver in system-config-printer is my intention. system-config-printer does not correctly reproduce the recommendation from OpenPrinting here.
Your result seems to confirm that the HPLIP errors are really due to overloading the printer's resources. So the task for the HPLIP developers here is to make the error output more clear.
Concerning the audit errors which you get now, they come from the AppArmor protection of CUPS. If you are still able to print via Samba to a printer connected to a Windows box, it is no problem. If not, you can turn off the AppArmor protection as a quick workaround:
sudo aa-complain cupsd
To turn it back on later do:
sudo aa-enforce cupsd
The AppArmor configuration of the current Hardy package of CUPS does not restrict the SMB backend any more, so the Samba-related errors will go away with a fully updated Hardy.
First, my name is Till and not Tim.
Changing the recommendation to a PCL driver in system- config- printer is my intention. system- config- printer does not correctly reproduce the recommendation from OpenPrinting here.
Your result seems to confirm that the HPLIP errors are really due to overloading the printer's resources. So the task for the HPLIP developers here is to make the error output more clear.
Concerning the audit errors which you get now, they come from the AppArmor protection of CUPS. If you are still able to print via Samba to a printer connected to a Windows box, it is no problem. If not, you can turn off the AppArmor protection as a quick workaround:
sudo aa-complain cupsd
To turn it back on later do:
sudo aa-enforce cupsd
The AppArmor configuration of the current Hardy package of CUPS does not restrict the SMB backend any more, so the Samba-related errors will go away with a fully updated Hardy.