Common Linux problems
Problem |
| Possible cause and solutions |
|
|
|
The machine does | • | Check if the printer driver is installed in |
not print. |
| your system. Open Unified Driver |
|
| configurator and switch to the Printers |
|
| tab in Printers configuration window to |
|
| look at the list of available printers. Make |
|
| sure that your machine is displayed on |
|
| the list. If not, please, invoke Add new |
|
| printer wizard to set up your device. |
| • | Check if the printer has started. Open |
|
| Printers configuration and select your |
|
| machine on the printers list. Look at the |
|
| description in the Selected printer pane. |
|
| If its status contains “(stopped)” string, |
|
| please, press the Start button. After that |
|
| normal operation of the printer should be |
|
| restored. The “stopped” status might be |
|
| activated when some problems in |
|
| printing occurred. For instance, this could |
|
| be an attempt to print a document when |
|
| a port is claimed by a scanning |
|
| application. |
| • | Check if the port is not busy. Since |
|
| functional components of MFP (printer |
|
| and scanner) share the same I/O |
|
| interface (port), the situation of |
|
| simultaneous access of different |
|
| “consumer” applications to the same port |
|
| are possible. To avoid possible conflicts, |
|
| only one of them at a time is allowed to |
|
| gain control over the device. The other |
|
| “consumer” will encounter “device busy” |
|
| response. You should open ports |
|
| configuration and select the port |
|
| assigned to your printer. In the Selected |
|
| port pane you can see if the port is |
|
| occupied by some other application. If |
|
| this is the case, you should wait for |
|
| completion of the current job or should |
|
| press Release port button, if you are sure |
|
| that the present owner is not functioning |
|
| properly. |
| • | Check if your application has special |
|
| print option such as |
|
| specified in the command line parameter |
|
| then remove it to print properly. For Gimp |
|
| |
|
| and edit command line parameter in the |
|
| command item. |
|
|
|
Problem | Possible cause and solutions |
|
|
Some color images | This is a known bug in Ghostscript (until |
come out all black. | GNU Ghostscript version 7.05) when the |
| base color space of the document is |
| indexed color space and it is converted |
| through CIE color space. Because |
| Postscript uses CIE color space for Color |
| Matching System, you should upgrade |
| Ghostscript on your system to at least GNU |
| Ghostscript version 7.06 or later. You can |
| find recent Ghostscript versions at |
| www.ghostscript.com. |
|
|
The machine does | It is a known problem that occurs when a |
not print whole pages | color printer is used on version 8.51 or |
and its output is half | earlier of Ghostscript, |
page printed. | reported to bugs.ghostscript.com as |
| Ghostscript Bug 688252. |
| The problem is solved in AFPL Ghostscript |
| v. 8.52 or above. Download the latest |
| version of AFPL Ghostscript from http:// |
| sourceforge.net/projects/ghostscript/ and |
| install it to solve this problem. |
|
|
Some color images | This is a known bug in Ghostscript (until |
come out in | GNU Ghostscript version 7.xx) when the |
unexpected color. | base color space of the document is |
| indexed RGB color space and it is |
| converted through CIE color space. |
| Because Postscript uses CIE color space |
| for Color Matching System, you should |
| upgrade Ghostscript on your system to at |
| least GNU Ghostscript version 8.xx or later. |
| You can find recent Ghostscript versions at |
| www.ghostscript.com. |
|
|
11.12 <Troubleshooting>
