[Ubuntu Wiki] Update of "DebuggingPrintingProblems" by pascal-devuyst

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "DebuggingPrintingProblems" page has been changed by pascal-devuyst:
http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=92&rev2=93

Comment:
printout > appout

   2. Disable the print queue with which you have the problem. Use system-config-printer (System -> Administration -> Printing in GNOME classic, Gear icon at the upper right of the screen -> Printers in Unity), right-click the appropriate printer icon, and click "Enabled" in the pop-up menu, so that the check mark disappears or run the command <<BR>> {{{$ cupsdisable <PRINTER>}}} <<BR>> in a terminal window (Replace "<PRINTER>" by the name of the print queue). This makes jobs staying in the queue so that you can capture them.
   3. Now print the job from your application. When the application has finished sending the job, check via the job viewer or the command <<BR>> {{{$ lpstat -o}}} <<BR>> whether it is in the queue.
   4. Display the content of CUPS' spool directory using the command <<BR>> {{{$ sudo ls -1 /var/spool/cups}}} <<BR>> (Enter your password when getting asked).
-  5. There should be exactly one file beginning with a "d". Copy this file to your home directory: <<BR>> {{{$ sudo cp /var/spool/cups/d... ~/printout}}} <<BR>> {{{$ sudo chmod 777 ~/printout}}}
+  5. There should be exactly one file beginning with a "d". Copy this file to your home directory: <<BR>> {{{$ sudo cp /var/spool/cups/d... ~/appout}}} <<BR>> {{{$ sudo chmod 777 ~/appout}}}
   6. Re-enable the print queue: <<BR>> {{{$ cupsenable <PRINTER>}}} <<BR>>
   7. If the file gets correctly printed now, try the above procedure with another file, we need a file where the problem occurs.
-  8. Check via the command <<BR>> {{{$ file ~/printout}}} <<BR>> what format the file is. It is usually PDF or PostScript. Display the file on the screen to see whether the problem already occurs (error message, missing characters, wrong colors, ...). If you see the problem already, the application is the culprit, assign your bug report to the application's package, otherwise assign it to the "cups" package.
+  8. Check via the command <<BR>> {{{$ file ~/appout}}} <<BR>> what format the file is. It is usually PDF or PostScript. Display the file on the screen to see whether the problem already occurs (error message, missing characters, wrong colors, ...). If you see the problem already, the application is the culprit, assign your bug report to the application's package, otherwise assign it to the "cups" package.
-  9. Attach the original file of your application and the ~/printout file to your bug report.
+  9. Attach the original file of your application and the ~/appout file to your bug report.
  
  = Getting the data which would go to the printer =