DebuggingPrintingProblems
|
Size: 938
Comment:
|
Size: 1748
Comment:
|
| 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}}} ---- * 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. |
== I. Printer detection == 1. Make sure that the printer is connected to your system and powered on. 2. Unplug the printer cable from your computer, open a terminal/console and enter this command: [[BR]] {{{$ tail -f /var/log/messages | tee ~/messages.log}}} 3. Reconnect the printer cable, you should see some messages appearing. 4. Press Ctrl-C to stop the logging. 5. Find out if your printer gets detected by CUPS: [[BR]] {{{$ lpinfo -v | tee ~/lpinfo.txt}}} 6. Attach {{{~/messages.log}}} and {{{~/lpinfo.txt}}} to the bug report. == II. Printingbuginfo == Attach the output of 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. == III. CUPS error_log == 1. Edit the file /etc/cups/cupsd.conf, find the section "loglevel" and change "info" 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. == IV. No or unexpected printing results == 1. Edit the file /etc/foomatic/filter.conf 2. Find the section 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]] {{{$ cd ~}}}[[BR]] {{{$ sudo chmod o+r foomatic-rip*}}} 6. Attach {{{~/foomatic-rip.log}}} and {{{~/foomatic-rip.ps}}} to the bug report. |
I. Printer detection
- 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
- Reconnect the printer cable, you should see some messages appearing.
- Press Ctrl-C to stop the logging.
Find out if your printer gets detected by CUPS: BR $ lpinfo -v | tee ~/lpinfo.txt
Attach ~/messages.log and ~/lpinfo.txt to the bug report.
II. Printingbuginfo
Attach the output of 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.
III. 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.
IV. No or unexpected printing results
- Edit the file /etc/foomatic/filter.conf
- Find the section debug and change "debug: 0" into "debug: 1"
- Try to print something.
View the file /tmp/foomatic-rip.ps with a postscript viewer: BR $ sudo evince /tmp/foomatic-rip.ps
Copy to home directory and change the permissions: BR $ sudo cp /tmp/foomatic-rip* ~ BR $ cd ~BR $ sudo chmod o+r foomatic-rip*
Attach ~/foomatic-rip.log and ~/foomatic-rip.ps to the bug report.
DebuggingPrintingProblems (last edited 2018-07-03 19:37:28 by vorlon)