DebuggingPrintingProblems

Differences between revisions 2 and 18 (spanning 16 versions)
Revision 2 as of 2007-02-19 09:34:41
Size: 938
Editor: 86-39-13-120
Comment:
Revision 18 as of 2007-03-06 16:12:24
Size: 3527
Editor: cF5A6BF51
Comment: merged in DebuggingPrintingErrors
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
 * Make sure that the printer is connected to your system and powered on.
 * Unplug the printer cable from your computer, open a terminal/console and enter this command: [[BR]] {{{$ tail -f /var/log/messages | tee ~/messages.log}}}
 * Find out if your printer gets detected by CUPS: [[BR]] {{{$ lpinfo -v | tee lpinfo.txt}}}
||<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]]||

= 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 '''Log``Level''' 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.


== Debugging printing errors ==

 * Try both in GNOME and KDE and report whether the problem appears on both or only on one of them. This helps to identify where in the chain of printing program the error may be located.

 * Debugging CUPS [http://www.linux-foundation.org/en/OpenPrinting/Database/ErrorLogFAQ]

 * Find your printers' URIs :
{{{
lpstat -v
}}}

 * Restart cupsd :
{{{
sudo /etc/init.d/cupsys restart
}}}
instead of
{{{
killall -HUP cupsd
}}}

Info from the kernel:
{{{
dmesg|grep lp0
}}}
If it indicates that ECP is used, please switch to EPP in the BIOS setup and try again.
If it doesn't show anything, do:
{{{
sudo modprobe lp
}}}
and try again.

 * Configure your printer with the CUPS configuration page: type [WWW] http://127.0.0.1:631/ into any browser.

= 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
Line 5: Line 86:
 * Provide the output from the printingbuginfo script for some useful information related to printing about your system 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 ==
 * Edit the file /etc/cups/cupsd.conf, find the section "loglevel" and change "info" to "debug", save the file
 * Restart CUPS: [[BR]] $ sudo /etc/init.d/cupsys restart
 * Try to print something.
 * Attach /var/log/cups/error_log to the bug report.
CategoryBugSquad

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.

Debugging printing errors

lpstat -v
  • Restart cupsd :

sudo /etc/init.d/cupsys restart

instead of

killall -HUP cupsd

Info from the kernel:

dmesg|grep lp0

If it indicates that ECP is used, please switch to EPP in the BIOS setup and try again. If it doesn't show anything, do:

sudo modprobe lp

and try again.

  • Configure your printer with the CUPS configuration page: type [WWW] http://127.0.0.1:631/ into any browser.

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)