DebuggingPrintingProblems

Differences between revisions 17 and 19 (spanning 2 versions)
Revision 17 as of 2007-02-22 01:12:46
Size: 2032
Editor: c-24-21-235-175
Comment:
Revision 19 as of 2007-03-09 19:09:28
Size: 2712
Editor: 86-39-44-79
Comment: Removed redundant section "Debugging printing errors"
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== I. Printer detection == ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]||
Line 3: Line 3:
=== USB printer === = Printer detection =

== USB printer ==
Line 13: Line 15:
=== Parallel port printer === == Parallel port printer ==
Line 21: Line 23:
== II. Printingbuginfo == = Printing bug info =
Line 24: Line 26:
== III. CUPS error_log == = CUPS error_log =
Line 30: Line 32:

= Known bugs =

Description of known issues, how to recognise them and stock responses/actions.

'''Open'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

'''Closed'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||


------
'''Also see:'''

 * DebuggingProcedures

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.

Printing bug info

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.

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.

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Bug#

Description

Action

TBD.

TBD.

TBD.

Closed

Bug#

Description

Action

TBD.

TBD.

TBD.


Also see:


CategoryBugSquad

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