Bug#892525: marked as done (cups-daemon: Cannot print with HPLIP backend)
Your message dated Thu, 29 Mar 2018 19:03:35 +0200
with message-id <85a7uqn79z.fsf@boum.org>
and subject line Re: Bug#892525: cups-daemon: Cannot print with HPLIP backend
has caused the Debian Bug report #892525,
regarding cups-daemon: Cannot print with HPLIP backend
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
892525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892525
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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).
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.
(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.)
Cheers,
--
intrigeri
--- End Message ---
--- Begin Message ---
Hi,
Brian Potkin:
> Hello intrigeri, thank you for caring about the printing system.
Thanks for your feedback!
I cannot reproduce this problem anymore so:
- I doubt AppArmor is involved (the policy has not changed recently).
- This bug report is not actionable so I'm closing it.
Cheers,
--
intrigeri
--- End Message ---
Reply to: