If you experiencing a problem with printing, please take a look at the [[Bugs/Common|common bugs]] page before filing a bug. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider [[#Filing_a_bug_report|filing a bug report]] to help us make Fedora run better on your hardware.

+

If you are experiencing a problem with printing, please take a look at the [[Bugs/Common|common bugs]] page before filing a bug. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider [[#Filing_a_bug_report|filing a bug report]] to help us make Fedora run better on your hardware.

== Identifying your problem area ==

== Identifying your problem area ==

Line 7:

Line 7:

=== Printing troubleshooter ===

=== Printing troubleshooter ===

−

The first thing to try is to run the printing troubleshooter: ''System > Administration > Printing'' from the main menu, then ''Help > Troubleshoot'' from the menu bar. This will ask a series of questions about the problem you are experiencing, with the aim of finding the reason for the problem.

+

The first thing to try is to run the printing troubleshooter.

+

Install system-config-printer:

+

<pre>

+

su -c 'yum install system-config-printer'

+

</pre>

+

Run it on the command line:

+

<pre>

+

su -c 'system-config-printer'

+

</pre>

+

system-config-printer is available from the menu on the following Fedora versions:

Then select ''Help > Troubleshoot'' from the menu bar. This will ask a series of questions about the problem you are experiencing, with the aim of finding the reason for the problem.

+

+

After following this process you will most likely end up with a {{filename|troubleshoot.txt}} file. '''This is the most helpful thing you can add to a bug report.'''

One step in this process is to print a test page. There is a button in the troubleshooter to print a test page for you, but if the problem you are seeing is specific to printing from a certain application, or printing a certain document, just go ahead and print from that application or print that particular document. The print job will appear in the troubleshooting window -- just put a tick in the box next to that print job to say that it is the one you are having trouble with.

One step in this process is to print a test page. There is a button in the troubleshooter to print a test page for you, but if the problem you are seeing is specific to printing from a certain application, or printing a certain document, just go ahead and print from that application or print that particular document. The print job will appear in the troubleshooting window -- just put a tick in the box next to that print job to say that it is the one you are having trouble with.

If the problem was not found automatically you will be given the option to save the diagnostic information collected during the troubleshooting process in a file named {{filename|troubleshoot.txt}}. If you report a bug you should attach this file, not compressed, with the MIME type set as text/plain.

If the problem was not found automatically you will be given the option to save the diagnostic information collected during the troubleshooting process in a file named {{filename|troubleshoot.txt}}. If you report a bug you should attach this file, not compressed, with the MIME type set as text/plain.

+

+

==== Getting debug information by other means ====

+

+

If you are unable to use the printing troubleshooter for whatever reason, here are the steps to follow in order to get debugging information.

+

+

1. Enable full debugging information with:

+

<pre>

+

su -c 'cupsctl LogLevel=debug2'

+

</pre>

+

+

2. Clear out the {{filename|error_log}} file with:

+

+

''Fedora 16 or later:''

+

<pre>

+

su -c 'systemctl stop cups.service'

+

su -c '>/var/log/cups/error_log'

+

su -c 'systemctl start cups.service'

+

</pre>

+

+

''Fedora 15 and older:''

+

<pre>

+

su -c '/sbin/service cups restartlog'

+

</pre>

+

+

3. You will now get debugging information sent to {{filename|/var/log/cups/error_log}} as you print files etc.

+

+

4. To turn off debugging information, do this:

+

<pre>

+

su -c 'cupsctl --no-debug-logging'

+

</pre>

+

+

5. {{filename|/var/log/cups/error_log}} is not world-readable, but the default CUPS configuration allows you to fetch it like this:

+

<pre>

+

wget http://localhost:631/admin/log/error_log

+

</pre>

=== What make and model is my printer? ===

=== What make and model is my printer? ===

Line 21:

Line 72:

</pre>

</pre>

−

This will output a series of blocks of lines, each one like this:

+

This command runs each of the backends in discovery mode, to get them to report devices they can automatically detect. This will output a series of blocks of lines, each one like this:

The line which identifies this particular model type is the one that start "device-id =".

+

The line which identifies this particular model type is the long one that starts "device-id =" (shown here wrapping over three lines).

+

+

Note that if your printer cannot be automatically detected, you may still be able to find out the Device ID by running the appropriate backend with the printer hostname as the argument. The '''usb''', '''parallel''', '''snmp''', and '''dnssd''' backends all try to report the actual Device ID given by the printer.

Device ID is in this case (see [http://www.cups.org/documentation.php/doc-1.5/man-backend.html backend(7)]) the last but one field.

+

+

=== Which driver am I using? ===

+

+

The PPD file for the printer queue can tell you which driver is in use. You can use this command to find out which driver is being used:

+

+

<pre>

+

grep -H '^*NickName:' /etc/cups/ppd/*.ppd

+

</pre>

+

+

You can also find this out using the '''system-config-printer''' application. Double-click on the icon for the queue and look at the ''Make and Model'' field.

+

+

To see the available drivers, click on the ''Change...'' button next to that field. You might find it useful to try another driver to see if that shows the same problem.

+

+

=== Finding where the problem lies ===

+

+

When a print job is processed it is sent through a chain of ''filters'' to convert the file into a format the printer can understand, and then finally sent to a ''backend'', a program which can transport the data to the printer. By slightly changing how you print you can try a different printing path to see if that changes anything. If it works around the problem, you know which area the problem was in -- include that information in a bug report so that we can fix it.

+

+

==== Application ====

+

+

Try printing from a different application to see if the problem goes away or if it occurs regardless of how a file is printed. Try printing the document from the command line using the '''lp''' command.

+

+

==== Document format ====

+

+

If you are having problems printing PDF files, try printing other types of file to see if the problem is with printing anything or if it is specific to printing PDF files. Try converting the file to a different format and printing that.

+

+

If the problem relates to printing text files, try removing/installing the paps package. This package provides an alternative text-to-PostScript filter to the one that comes with CUPS.

+

+

===== Running filters by hand =====

+

+

More advanced users may like to try running the CUPS filters by hand and examining the data file at each step as it is converted between different formats. Here is an example of doing this for a gutenprint queue named pqueue with the CUPS test page which is its own special MIME type, application/vnd.cups-banner:

+

+

First you need to know the filter pipeline for application/vnd.cups-banner --> printer/pqueue (output MIME type).

+

You can either [[#Getting_debug_information_by_other_means|enable debugging]], print a test page, look into /var/log/cups/error_log and you'll find something similar to:

Here, {{command|evince}} or {{command|okular}} can be used to examine the output after the first two filters, {{command|rasterview}} can be used to examine the output of the third filter, and the last filter's output must be inspected by hand or sent directly (lpr -oraw out.prn) to the printer.

+

+

==== Driver ====

+

+

If you have access to a different make/model of printer it might be worth trying to see if the problem occurs on both of them or just one. This can give an indication about whether it is a problem with a particular driver, or if it is a more general problem.

+

+

Even if you only have access to the one printer there is often a choice of drivers to use for a given printer model, and trying each one in turn can be useful in narrowing down the problem. See [[#Which_driver_am_I_using.3F|above]] for how to do that.

+

+

===== Foomatic =====

+

+

For Foomatic drivers you can try enabling Foomatic debugging by editing the file {{{filename|/etc/foomatic/filter.conf}}} and adding a line:

+

+

<pre>

+

debug: 1

+

</pre>

+

+

Next time you print a job to a queue using foomatic the debugging will be put in {{{filename|/tmp/foomatic-rip.log}}}, and the input file as received by foomatic-rip will be in {{{filename|/tmp/foomatic-rip.ps}}}.

+

+

==== Backend (job transport) ====

+

+

It may be possible for you to try a different backend. Using '''system-config-printer''', double-click on the printer queue icon and click the ''Change...'' button next to the ''Device URI'' field. You may see a ''Connection'' expander arrow near the bottom right hand corner of the window -- click that to see which backends are available. For USB-connected HP printers, typically either of the '''hp''' and '''usb''' backends can be used.

+

+

For network printers you may have different protocols you can try.

+

+

* '''socket''' is for HP JetDirect (usually port 9100)

+

* '''lpd''' is for older style UNIX print shares

+

* '''smb''' is for CIFS shares from Windows systems

+

* '''ipp''' is for Internet Printing Protocol-enabled devices and also for other CUPS servers

+

** You can capture the IPP traffic with tcpdump like this (the interface name may differ from '''p4p1'''):

Problems involving printing may relate to several components: the configuration GUI is [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=system-config-printer system-config-printer], back end components include [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=cups cups] (the actual printing sytem used by default), [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=foomatic foomatic] (the main driver and printer information database), and [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=hpijs hpijs] (the drivers used for HP printers). If you are not sure, make your best guess.

+

=== Deciding which component ===

+

+

Problems involving printing may relate to several components.

+

+

The configuration GUI (See [[#Configuration_tool|above]]) is either [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=control-center GNOME 3 System Settings application] or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=system-config-printer system-config-printer]. These packages also provide the printer applet, handle automatic queue creation, and disable/enable queues when USB printers are disconnected and reconnected.

+

+

Most GTK+ applications use the GTK+ print dialog. If the problem occurs when using GTK+ applications but not when printing from the command line or from another non-GTK+ application, the problem should probably be reported against [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=gtk2 gtk2]. If the problem occurs with only one GTK+ application, and other GTK+ applications print fine, the bug should be filed against that particular application.

+

+

If the problem only happens with PDF files, the bug may well be in [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=poppler poppler] (the CUPS '''pdftops''' filter is a wrapper around one of the poppler utility programs).

+

+

Report bugs only seen using the '''smb''' backend against [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=samba samba].

+

+

For bugs only seen when using the '''hp''' backend, or the hpijs or hpcups drivers, select [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=hplip hplip] for the component.

* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=gutenprint gutenprint] (a driver that supports very many printers)

+

+

For anything else, or if you are not sure, choose [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=cups cups] or use your best guess.

+

+

=== Other information to include ===

Be prepared to include some information about your system as well. Some of this can be gathered automatically using the [[#Printing_troubleshooter|printing troubleshooter]], but you may also need to include other information such as:

Be prepared to include some information about your system as well. Some of this can be gathered automatically using the [[#Printing_troubleshooter|printing troubleshooter]], but you may also need to include other information such as:

Line 42:

Line 235:

* the PPD file for the print queue (from the {{filename|/etc/cups/ppd}} directory)

* the PPD file for the print queue (from the {{filename|/etc/cups/ppd}} directory)

* the document you are attempting to print -- if this is large, please try to see if the problem also occurs with a smaller document

* the document you are attempting to print -- if this is large, please try to see if the problem also occurs with a smaller document

+

+

Some example documents can be found in [[:Category:Printing_Test_Cases|the Printing Test Cases category]].

+

+

=== Further reading ===

+

+

The [[Printing|main printing page]] has more information about how printing works in Fedora.

[[Category:Debugging|P]] [[Category:How to]]

[[Category:Debugging|P]] [[Category:How to]]

Revision as of 17:55, 20 August 2013

Foreword

If you are experiencing a problem with printing, please take a look at the common bugs page before filing a bug. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug report to help us make Fedora run better on your hardware.

Identifying your problem area

Printing troubleshooter

The first thing to try is to run the printing troubleshooter.
Install system-config-printer:

su -c 'yum install system-config-printer'

Run it on the command line:

su -c 'system-config-printer'

system-config-printer is available from the menu on the following Fedora versions:

Activities > Print Settings (Fedora 18, 19), or

Applications > Other > Printing from the GNOME Shell overview (Fedora 15), or

System > Administration > Printing from the GNOME menu (Fedora 14 and earlier).

Then select Help > Troubleshoot from the menu bar. This will ask a series of questions about the problem you are experiencing, with the aim of finding the reason for the problem.

After following this process you will most likely end up with a troubleshoot.txt file. This is the most helpful thing you can add to a bug report.

One step in this process is to print a test page. There is a button in the troubleshooter to print a test page for you, but if the problem you are seeing is specific to printing from a certain application, or printing a certain document, just go ahead and print from that application or print that particular document. The print job will appear in the troubleshooting window -- just put a tick in the box next to that print job to say that it is the one you are having trouble with.

If the problem was not found automatically you will be given the option to save the diagnostic information collected during the troubleshooting process in a file named troubleshoot.txt. If you report a bug you should attach this file, not compressed, with the MIME type set as text/plain.

Getting debug information by other means

If you are unable to use the printing troubleshooter for whatever reason, here are the steps to follow in order to get debugging information.

The line which identifies this particular model type is the long one that starts "device-id =" (shown here wrapping over three lines).

Note that if your printer cannot be automatically detected, you may still be able to find out the Device ID by running the appropriate backend with the printer hostname as the argument. The usb, parallel, snmp, and dnssd backends all try to report the actual Device ID given by the printer.

Which driver am I using?

The PPD file for the printer queue can tell you which driver is in use. You can use this command to find out which driver is being used:

grep -H '^*NickName:' /etc/cups/ppd/*.ppd

You can also find this out using the system-config-printer application. Double-click on the icon for the queue and look at the Make and Model field.

To see the available drivers, click on the Change... button next to that field. You might find it useful to try another driver to see if that shows the same problem.

Finding where the problem lies

When a print job is processed it is sent through a chain of filters to convert the file into a format the printer can understand, and then finally sent to a backend, a program which can transport the data to the printer. By slightly changing how you print you can try a different printing path to see if that changes anything. If it works around the problem, you know which area the problem was in -- include that information in a bug report so that we can fix it.

Application

Try printing from a different application to see if the problem goes away or if it occurs regardless of how a file is printed. Try printing the document from the command line using the lp command.

Document format

If you are having problems printing PDF files, try printing other types of file to see if the problem is with printing anything or if it is specific to printing PDF files. Try converting the file to a different format and printing that.

If the problem relates to printing text files, try removing/installing the paps package. This package provides an alternative text-to-PostScript filter to the one that comes with CUPS.

Running filters by hand

More advanced users may like to try running the CUPS filters by hand and examining the data file at each step as it is converted between different formats. Here is an example of doing this for a gutenprint queue named pqueue with the CUPS test page which is its own special MIME type, application/vnd.cups-banner:

First you need to know the filter pipeline for application/vnd.cups-banner --> printer/pqueue (output MIME type).
You can either enable debugging, print a test page, look into /var/log/cups/error_log and you'll find something similar to:

Here, evince or okular can be used to examine the output after the first two filters, rasterview can be used to examine the output of the third filter, and the last filter's output must be inspected by hand or sent directly (lpr -oraw out.prn) to the printer.

Driver

If you have access to a different make/model of printer it might be worth trying to see if the problem occurs on both of them or just one. This can give an indication about whether it is a problem with a particular driver, or if it is a more general problem.

Even if you only have access to the one printer there is often a choice of drivers to use for a given printer model, and trying each one in turn can be useful in narrowing down the problem. See above for how to do that.

Foomatic

For Foomatic drivers you can try enabling Foomatic debugging by editing the file /etc/foomatic/filter.conf and adding a line:

debug: 1

Next time you print a job to a queue using foomatic the debugging will be put in /tmp/foomatic-rip.log, and the input file as received by foomatic-rip will be in /tmp/foomatic-rip.ps.

Backend (job transport)

It may be possible for you to try a different backend. Using system-config-printer, double-click on the printer queue icon and click the Change... button next to the Device URI field. You may see a Connection expander arrow near the bottom right hand corner of the window -- click that to see which backends are available. For USB-connected HP printers, typically either of the hp and usb backends can be used.

For network printers you may have different protocols you can try.

socket is for HP JetDirect (usually port 9100)

lpd is for older style UNIX print shares

smb is for CIFS shares from Windows systems

ipp is for Internet Printing Protocol-enabled devices and also for other CUPS servers

You can capture the IPP traffic with tcpdump like this (the interface name may differ from p4p1):

Most GTK+ applications use the GTK+ print dialog. If the problem occurs when using GTK+ applications but not when printing from the command line or from another non-GTK+ application, the problem should probably be reported against gtk2. If the problem occurs with only one GTK+ application, and other GTK+ applications print fine, the bug should be filed against that particular application.

If the problem only happens with PDF files, the bug may well be in poppler (the CUPS pdftops filter is a wrapper around one of the poppler utility programs).

For anything else, or if you are not sure, choose cups or use your best guess.

Other information to include

Be prepared to include some information about your system as well. Some of this can be gathered automatically using the printing troubleshooter, but you may also need to include other information such as:

the PPD file for the print queue (from the /etc/cups/ppd directory)

the document you are attempting to print -- if this is large, please try to see if the problem also occurs with a smaller document