Thanks. We are getting there, but the solution is still elusive. I did the apparmor_parser command, then tried to print. Result: printer not connected error
So I deleted and reinstalled printer, and rebooted. Surprise: apparmor again denied execution after reboot. So I did apparmor_parser Result: almost OK. Printer came to life, tried to do something, then cups reported error dmesg indicated segmentation fault in print driver I verified the printdriver file with diff comparing it with the same file on my FC3 installation where the printer works - no difference. My FC3 installation is all bastardized. It is my sandbox. I compiled cups from source, it is 1.4.6 - but it works. Attached are two files: (1) dmsg outputs, and (2) print troubleshooter saved Aside from this it looks like reboot restores apparmor behaviour to original state and we have to do manual apparmor_parser which is definitely a bug. Thanks for your interest in this problem. ** Attachment added: "dmesg outputs" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+attachment/3698836/+files/Lexmark-apparmor.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
