Hello intrigeri, thank you for caring about the printing system.
On Sat 10 Mar 2018 at 08:50:45 +0100, intrig...@debian.org wrote: > Package: cups-daemon > Version: 2.2.6-5 > Severity: normal > > Hi, > > for now this bug report is mostly a note to myself (and to whoever > wants to help investigating/fixing this problem). I don't know how much help I will be but I'll give it a try. > A few days ago on an up-to-date sid system I was unable to print with > the HPLIP backend. In the Journal I saw: > > /hpfax[4306]: [4306]: error: Failed to create /var/spool/cups/tmp/.hplip > > I don't know yet if this issue is AppArmor-related and will > investigate once I have access to that printer again in a few days. > /usr/lib/cups/backend/hpfax is supposed to be confined under the > third_party child profile which allows any "file" operation so in > theory AppArmor cannot trigger the above log line. Firstly: not being able to print and the error message may not be linked. Secondly: there is Debian bug report #789286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789286 but it is not choc-a-bloc full of detail; the bug submitter wasn't pressed for details on any inability to print. Thirdly: LP #1490321 doesn't really lead anywhere: https://bugs.launchpad.net/hplip/+bug/1490321 Fourthly: FWIW, I'd guess AppArmor need not be involved. (But that is for you to decide). You should not need access to the printer. The wiki has details but it is only necessary in most cases to set up a print queue: lpadmin -p test -v file:/dev/null -E -m <PPD_for_the_printer> Then lp -d test <file> and look at the error_log. Get the printer's PPD from 'lpinfo -m'. > (Probably unrelated, on cupsd startup I see: > > audit[14628]: AVC apparmor="DENIED" operation="capable" > profile="/usr/sbin/cupsd" pid=14628 comm="cupsd" capability=12 > capname="net_admin" > > I'll file a dedicated bug (+patch) for that one once I've confirmed > it's orthogonal to the HPLIP issue.) Not seen that. Cheers, Brian.
