I was hoping that I could guide someone knowledgeable through some logical steps, and, possibly find a simple error in one of my config files. My reasoning follows:
The output in the cups-pdf_log file shows that the output pdf file is created (4th line, not counting line wraps). It shows later, on the 6th DEBUG line, that the output pdf file is unlinked. Because these lines are in the cups-pdf_log file, it implies that (a) I specified the PDF directory properly (otherwise it would be writing somewhere else), (b) why would cups-pdf report that it's unlinking the file? If apparmor were doing the unlinking, wouldn't that fact be logged in some apparmor log and not the cups-pdf_log file? I'm thinking that it's one of: 1. bad options to ghostscript/ps2pdf. The command line is shown above from the log file. I went through the man page and didn't see any option for deleting a PDF after it's created. 2. Bad configuration for cups-pdf. I would expect that cups would delete temporary print files after a file is sent to a printer, but it shouldn't do that when creating a PDF. I attached the config file. Can you diff with yours? 3. bad configuration of ghostscript/ps2pdt. Perhaps some necessary module wasn't installed. I had to install 16.10 from scratch, because upgrading from 16.04 didn't work. 4. something to do with apparmor. I have no knowledge of how to tweak apparmor. I attached my config file. Can you diff with yours? Thanks for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662660 Title: cups-pdf not creating any output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/1662660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs