Changes between Version 12 and Version 13 of CupsFaq


Ignore:
Timestamp:
Oct 14, 2013, 12:07:02 AM (11 years ago)
Author:
Alex Taylor
Comment:

Added 3.6

Legend:

Unmodified
Added
Removed
Modified
  • CupsFaq

    v12 v13  
    3636<li><a href="#3_4">3.4.  Why do pages come out all black, or shrunk to postage-stamp size?</a>
    3737<li><a href="#3_5">3.5.  When printing documents from Lotus WordPro (SmartSuite), certain text like equations is missing.  Why is this?</a>
     38<li><a href="#3_6">3.6.  I can print a test page from the CUPS web interface, but when I print from an application, nothing happens.  How can I find out what's wrong?</a>
     39
    3840</ul></p>
    3941
     
    786788<h3>3.5.  When printing documents from Lotus WordPro (SmartSuite), certain text like equations is missing.  Why is this?</h3>
    787789<p>This appears to be a bug in SmartSuite; specifically, it is failing to properly translate the device coordinates from the screen to the printer when it generates the commands for drawing certain items. The eCups printer drivers incorporate a workaround for this by setting the default printer resolution to 1440 dpi, which corresponds to the coordinate system SmartSuite uses on-screen.  However, if your printer model defines an explicit default resolution, the latter may get selected instead.
    788 <p>If you encounter this problem: in the CUPS administration console, and in the driver properties, try verifying that your printer resolution is set to 1440 dpi.  (If 1440 dpi is not one of the available selection, you may need to select a different printer model.)
     790<p>If you encounter this problem: in the CUPS administration console, and in the driver properties, try verifying that your printer resolution is set to 1440 dpi.  (If 1440 dpi is not one of the available selections, you may need to select a different printer model.)
     791
     792<p><br><a name="3_6"></a>
     793<h3>3.6.  I can print a test page from the CUPS web interface, but when I print from an application, nothing happens.  How can I find out what's wrong?</h3>
     794<p>The simplest cause could be a mismatch between the name used in the PM printer object's CUPS port, and the actual name of the CUPS printer.  The two must match.  To see if this is the case, try the following:
     795<ol>
     796<li>Go to the desktop printer object, right-click on it and choose Properties.
     797<li>Go to the 'Output port' page and locate the port that is currently selected (highlighted).  Right-click on the port icon and choose  Properties.
     798<li>Take note of the value in the field labelled 'CUPS printer name'.
     799<li>Open the CUPS web interface in your browser and go to the <a href="http://localhost:631/printers/">Printers</a> page.     
     800<li>Make sure that the name of the printer shown on this page is exactly the same as the value you noted in step (3).  If it is not the same,   change the value in the port properties to match what you see in CUPS.
     801</ol>
     802<p>If the above does not help, you can try a more advanced diagnostic technique, as follows:
     803<ol>
     804<li>Open the desktop printer object, right-click inside it and select <i>Change status</i> -> <i>Hold</i>.
     805<li>Print something to the printer.  A job will appear in the printer object (but won't print because the printer is held).
     806<li>Find out what your physical PM spooler directory is by opening the <i>Spooler</i> object in your "System Setup" WPS folder; the value shown for "spool path" on the first page indicates the spooler directory (it is probably either \SPOOL or \VAR\SPOOL on your boot drive)
     807<li>Go to the spooler directory identified above (using your preferred file manager or a command prompt) and locate the subdirectory corresponding to the printer object.  (If you have multiple printer objects, the correct subdirectory should be the one which contains a pair of files with names like <tt><i>number</i>.SPL</tt> and <tt><i>number</i>.SHL</tt>.)
     808<li>Copy the <tt><i>number</i>.SPL</tt> file in this directory to some other location, and rename it to something like <tt>cupstest.ps</tt>.
     809<li>Go back into the desktop printer object, delete the paused print job, and then change the printer setting back to <i>Change status</i> -> <i>Release</i>.
     810<li>Try printing the file you obtained in step 5 with the following command:
     811<pre>cupslpr -H <i>printername</i> cupstest.ps</pre>
     812where '<i>printername</i>' is the name of the printer as it appears on the CUPS <a href="http://localhost:631/printers/">Printers page</a>.
     813</ol>
     814<p>If the file prints using this technique, then you must have a configuration problem somewhere in the linkage between the printer object and CUPS.  If it doesn't print, it probably indicates that the generated PostScript code is faulty in some way, and you may need to change or upgrade the presentation driver (ECUPS.DRV/ECUPS-HP.DRV or whatever else you are using).
    789815}}}