[Ubuntu Wiki] Update of "DebuggingPrintingProblems" by till-kamppeter

Ubuntu Wiki noreply at ubuntu.com
Thu Oct 7 15:14:36 BST 2010

Dear Wiki user,

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

The following page has been changed by till-kamppeter:

  = AppArmor Protection of the printing system =
  From Gutsy on the security of the CUPS printing system is improved by using App``Armor. Unfortunately, the configuration is not perfect yet, especially if third-party printer drivers are used. If you have any problems with printing, try deactivating the App``Armor protection with {{{sudo aa-complain cupsd}}}. If this helps, look for messages containing '''audit''' in the {{{/var/log/messages}}} file. These show which components are accessed by the printing system for which there is no explicit permission given in {{{/etc/apparmor.d/usr.sbin.cupsd}}}. You can re-activate App``Armor via {{{sudo aa-enforce cupsd}}}. Report a bug, about the package '''cups''' ('''cupsys''' on 8.04 and older), so that we can correct the default configuration of App``Armor.
+ = Capturing print job data =
+ Oftenn it is needed to find out what actually got sent to the printer in order to determine whether the problem is caused by the application or by the printing subsystem. For that it is the easiest way to capture the job data from the application so that it can analyzed whether it is already broken or not. To do so, follow these steps: <<BR>>
+  1. Clear the print queues from old jobs. Either use the job viewer or run the command <<BR>> {{{$ cancel -a}}} <<BR>> in a terminal window.
+  2. Disable the print queue with which you have the problem. Use system-config-printer (System -> Administration -> Printing), 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}}}
+  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.
+  9. Attach the original file of your application and the ~/printout file to your bug report.
  = Known bugs =
  Description of known issues, how to recognise them and stock responses/actions.
  ## '''Open'''
- ||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
+ ##||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
- || [[https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/29050|29050]] || Parallel/LPT printer not detected in Dapper and Edgy. Fixed in Feisty. || add "ppdev" to {{{/etc/modules}}} ||
+ ##|| [[https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/29050|29050]] || Parallel/LPT printer not detected in Dapper and Edgy. Fixed in Feisty. || add "ppdev" to {{{/etc/modules}}} ||
  ## '''Closed'''
  ## ||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||

More information about the Ubuntu-bugsquad mailing list