DebuggingPrintingProblems

Differences between revisions 15 and 16
Revision 15 as of 2007-02-19 12:59:23
Size: 2561
Editor: 86-39-13-120
Comment: initial version
Revision 16 as of 2007-02-20 22:39:54
Size: 2008
Editor: 86-39-44-122
Comment: Remove section IV
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:

== IV. No or unexpected printing results ==
 1. Edit the file /etc/foomatic/filter.conf
 2. Find the line that starts with debug and change '''debug: 0''' into '''debug: 1'''
 3. Try to print something.
 4. View the file /tmp/foomatic-rip.ps with a postscript viewer: [[BR]] {{{$ sudo evince /tmp/foomatic-rip.ps}}}
 5. Copy to home directory and change the permissions: [[BR]] {{{$ sudo cp /tmp/foomatic-rip* ~}}} [[BR]] {{{$ sudo chmod o+r ~/foomatic-rip*}}}
 6. Attach {{{~/foomatic-rip.log}}} and {{{~/foomatic-rip.ps}}} to the bug report.

I. Printer detection

USB printer

  1. Make sure that the printer is connected to your system and powered on.
  2. Open a terminal/console and check if the usb kernel modules are loaded: BR $ lsmod | grep usb

  3. Unplug the USB printer cable from your computer and enter this command: BR $ tail -f /var/log/messages 

  4. Reconnect the USB printer cable, you should see some messages appearing.
  5. Press Ctrl-C to stop the logging.
  6. Find out if your printer gets detected by CUPS: BR $ lpinfo -v

  7. Attach the output of the above commands to the bug report.

Parallel port printer

  1. Make sure that the printer is connected to your system and powered on.
  2. Open a terminal/console and check if the lp and ppdev kernel modules are loaded: BR $ lsmod | grep lp

  3. Check if the kernel detected the parallel port during bootup: BR $ cat /var/log/messages | grep par 

  4. Find out if your printer gets detected by CUPS: BR $ lpinfo -v

  5. Attach the output of the above commands to the bug report.

II. Printingbuginfo

Attach the output of the printingbuginfo script for some useful information about your system related to printing like the version of Ubuntu you use, configured printers and the versions of important printing packages installed. The printingbuginfo script can be found here: https://wiki.ubuntu.com/PrintingBugInfoScript.

III. CUPS error_log

This is a file where CUPS writes information about what it is doing. Almost all printing problems can be diagnosed from the error log, so it is the first place to look to start solving problems. To be useful, you must change the logging level: BR

  1. Edit the file /etc/cups/cupsd.conf, find the line LogLevel and change it to debug, save the file.

  2. Restart CUPS: BR $ sudo /etc/init.d/cupsys restart

  3. Try to print something.
  4. Attach /var/log/cups/error_log to the bug report.

DebuggingPrintingProblems (last edited 2018-07-03 19:37:28 by vorlon)