I reproduced the situation, and get the same error with beh:/1/0/120/socket:myprinter:9100. However, it does not cause an AppArmor error message in dmesg, and rightfully disabling apparmor does not fix the situation either.
The file path looks fishy, why does it try to put the temporary file into / ? -- Cups backend 'beh' broken when apparmor profile enabled. https://bugs.launchpad.net/bugs/268284 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
