I'm going to take a chance that the problem I found on 11.10 is related
to this bug. I am posting here although cups-pdf has generated many
other discussions elsewhere where various suggestions have been made
with respect to file permissions, SELinux, Apparmor, etc. As is usually
the case, I tried several until finding "the main thing". I'm too tired
to retrace my steps and see if any of the other suggestions are actually
needed, but the problem I found was definitely a show-stopper.
As distributed, /etc/cups/cups-pdf.conf allows the path for gs to
default to /usr/bin/gs and that is not correct on my 11.10 system where
the correct path to gs is /usr/local/bin/ga. I see in you
CupsErrorLog.txt file that your system is similarly configured from this
line:
Ghostscript command line: /usr/bin/gs
The following is a diff of the change to cups-pdf-conf that did the
trick for me:
224c224
< GhostScript /usr/bin/gs
---
> GhostScript /usr/local/bin/gs
Clues that you may have this problem are found in /var/log/cups/cups-
pdf_log after setting LogType to 7 in cups-pdf.conf. Check your log file
for the debug line showing how gs is invoked and confirm that the path
is "/usr/bin/gs". If you, like me, have a system where the path should
be "/usr/local/bin/gs", then the PDF print will fail full stop. Another
clue is that the "[DEBUG] output file unlinked" line right after
invoking gs looks something like this:
{your date and time} [DEBUG] output file unlinked (/{whatever your home
directory is}/PDF/{whatever the OutputFile name was for gs})
The output file is being deleted because the gs invocation failed
(silently, as far as the cups-pdf_log file is concerned ).
Finally, you will see in the log file:
[ERROR] failed to set file mode for PDF file (non fatal) {your output
file name}
I'm slightly amused that cups records this as non-fatal as in "IT DIDN'T
WORK". While it is true that the file mode could not be set, this is not
a permission problem as much as it's the problem of trying to set
permissions on a non-existent file .
I spent a lot of time on this problem and never found another post that
came to this conclusion. I hope this saves you some trouble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663534
Title:
Printing errors after upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/663534/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
