On 3/3/25 09:34, Martin-Éric Racine wrote:
On Fri, 14 Jul 2023 13:46:22 -0400 "Eric W. Bates" <er...@ericx.net> wrote:
Package: printer-driver-cups-pdf
Version: 3.0.1-14
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Installed with apt.
Modified cups-pdf.conf to print to ${HOME}/tmp/cups-pdf
Attempt to print.
"Backend failed"
Increased cupsd.conf LogLevel to "debug"
Attempt to print.
"Backend failed"
Deleted PDF printer from cups
Forced reinstall of printer-driver-cups-pdf
Attempt to print.
"Backend failed"
Remove edit from cups-pdf.conf (e.g. back to default destination)
Attempt to print.
"Backend failed"
Attempt to find command line invocation in order to perhaps see a more useful
error message.
invoke:
# lpstat -p -d
printer isxerox-8145 is idle. enabled since Fri 14 Jul 2023 12:54:50 PM EDT
printer PDF is idle. enabled since Fri 14 Jul 2023 01:24:33 PM EDT
Backend failed
system default destination: PDF
Most information from /var/log/cups/error_log:
D [14/Jul/2023:12:59:27 -0400] [Job 7] PID 963955
(/usr/lib/cups/filter/pdftops) exited with no errors.
D [14/Jul/2023:12:59:27 -0400] [Job 7] PID 963956
(/usr/lib/cups/backend/cups-pdf) crashed on signal 11.
W [14/Jul/2023:12:59:27 -0400] [Job 7] Backend returned status -139 (crashed)
A little frustrating because there is so little information; but I will happily
execute anything you request.
Have you modified the AppArmor profile to match the path change? See
the NEWS and README for more info.
Martin-Éric
That's an excellent suggestion.
Where would I find NEWS or README?
I'm assuming they are part of the dpkg?
Found /usr/share/doc/printer-driver-cups-pdf/README.Debian (there is no
NEWS in the dpkg), and it does have a discussion of apparmor.
It says that if apparmor were the culprit, there would be messages in
dmesg 'audit[11578]: AVC apparmor="DENIED" ...' and there are no
messages from apparmor in dmesg at all other than things like "[
0.070165] AppArmor: AppArmor initialized"
I was trying to print to ~/tmp/cups-pdf/ and the existing apparmor
(/etc/apparmor.d/usr.sbin.cupsd) has an explicit allow for cups-pdf
already which looks like it should work:
# allow read and write on almost anything in @{HOME} (lenient, but
# private-files-strict is in effect), to support customized "Out"
# setting in cups-pdf.conf (Debian#940578)
#include <abstractions/private-files-strict>
@{HOME}/[^.]*/{,**/} rw,
@{HOME}/[^.]*/** rw,
I've also removed the "Out" in cups-pdf.conf and fallen back to the
default of /var/spool/cups-pdf/${USER} and there is still no output.
/var/spool/cups-pdf doesn't even get a folder with my account name.
There are no errors anywhere that I can find.
