The never-ending story here is the cpdftocps CUPS filter according to
your error_log and this filter turns the incoming PDF into PostScript
with the help of Poppler's pdftops command line utility.
So I tried to convert your file directly at the command line, using
pdftops cesifo1_wp1249-1.pdf
which takes a very long time using 100% CPU. During that time there is
no even data stream, the output file, growing to a final size of around
4 MB, hangs for a long time on 2.2 MB. Perhaps the printer times out the
connection while not receiving data for several minutes.
XPDF probably habgs on the same problem as pdftops as both XPDF and
Poppler use the same code for rendering, and printing out of XPDF is
terning the PDF to PostScript as running pdftops is.
To see whether the process is really infinite for you or simply too slow
so that the printer perhaps drops the connection, try the following:
Clean the queue with "cancel -a" and assure that it is enabled by
enabling it with systenm-config-printer or via "cupsenable <queue>".
Make sure that your CUPS logging is still in debug mode. Check also that
no disk partition is full ("df -h"). Then print the job again, wait
until the process seems to hang (observe your error_log). A sson as this
happens, run "top" and see whether there are processes taking all or at
least a significant amount of CPU and/or memory. Do "ps auxwww| grep
<process number>" to obtain the full command lines of these processes.
Post the command lines here.
Do not kill the print job. Leave it in the queue for at least one night.
Perhaps it even finishes and prints after some hours.
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
file won't print using any method
https://bugs.launchpad.net/bugs/488710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
