Everyone who has this problem please, I need the following information: 1. The file you tried to print. If you did not supply it yet, please attach it to the bug report. If the problem occurs for you directly after boot, please you have a file from the last session still in the print queue. You can find all stuck files in the print spool directory:
mkdir spoolfiles sudo cp /var/spool/cups/d* spoolfiles/ sudo chmod 777 spoolfiles/* Attach these files to this bug report. 2. How did you print? Which application did you use, which settings? 3. What is your printer/driver? Please attach the PPD file from /etc/cups/ppd/. 4. What is the Ghostscript command line. As sson as Ghostscript is running crazy, run the shell command "top" to see the offending "gs" process and note its process number. Then leave "top" with "q" and get the full Ghostscript command line via the shell command ps auxwww | grep <process number> Post the Ghostscript command line here. 5. Get an error_log in debug mode as described on https://wiki.ubuntu.com/DebuggingPrintingProblems in the "CUPS error_log" section. CUPS must be in debug mode while the offending job takes place. So clean up cancel -a sudo killall -9 gs set CUPS into debug mode and print the offending file again. As soon as the problem occurs, attach error_log and do also the steps 1-4. -- Process 'gs' begins taking 100% CPU and loading up vast amounts of RAM on CUPS restart https://bugs.launchpad.net/bugs/463059 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
