On Wed, May 09, 2007 at 11:05:01AM +1000, George Osvald wrote: > Thank you Seth. That was very helpful. Everything works now ewxcept for > printing. My CUPS server still says: > /usr/lib/cups/filter/foomatic-rip failed > when I try to print to my HP Officejet.
Great! Progress! :) Are there any REJECTING messages from AppArmor in your /var/log/audit/audit.log or /var/log/messages files that are generated by attempts to print? If so, the fastest way to get working again is to put the profiles that are rejecting your attempts to print into learning mode with the 'aa-complain' utility (perhaps just 'complain', I forget when we added the 'aa-' symlink :). They will look something like this: type=APPARMOR msg=audit(1174508205.298:1791): REJECTING r access to /bin/ (ls(16552) profile /tmp/ls active /tmp/ls) (This is just a simple line from a test profile for /tmp/ls, completely meaningless.. :) Where the profile is said to be /tmp/ls, I would find those lines in your system from failed print attempts, and use aa-complain for those: $ sudo aa-complain /home/sarnold/crm/crm/bin/crm Setting /home/sarnold/crm/crm/bin/crm to complain mode. $ Now you can try to print, run aa-logprof, answer some questions, and when you're all done, place the profiles back into enforce mode: $ sudo aa-enforce /home/sarnold/crm/crm/bin/crm Setting /home/sarnold/crm/crm/bin/crm to enforce mode. $ And give it one last test to make sure it's all working fine. :) Thanks George
pgpHJCRVBzrK5.pgp
Description: PGP signature
