Red Hat Bugzilla – Bug 111340
CUPS/Samba with HP L1300 driver generates raw postscript
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
Setting a printer up to print via samba (on a Red Hat 9 server) on a
HP Laserjet 1300 works fine as long as I choose the "generic
postscript" driver. If I choose manufacturer and model -- HP/Laserjet
1300 -- and the postscript driver, it seems like I get an extra level
of postscript generation: the printer spews out the raw postscipt code
directly on paper.
The problem is not serious for me; going back to the
manufaturer-independent "generic postscrip" driver works fine.
Printing from other machines (including Windows XP clients) works
fine, so I guess it's not the server's own cups implementation that is
Version-Release number of selected component (if applicable):
Standard fedora core 1
Steps to Reproduce:
Setup printer via redhat-config-printer, choose "windows printer",
choose the relevant server and printer, choose HP/Laserjet 1300,
postscript driver, print test sheet.
Raw postscript output from printer.
Processed postscript output.
Does 'raw print queue' work? There must be some way for the printing
configuration tool to be able to work out when that is needed. :-/
I'm having the same trouble with my LaserJet 1100. I setup a normal
print queue on my computer using local LPT1 port. lpr something.ps
works just fine. Enable lpd support on my computer. Goto another
linux box. Setup a queue on other computer as a 'raw printer queue'
or a 'postscript printer' queue and when the test page comes through I
get postscript on the printer instead of the test page.
It's exactly as if remote print jobs are NOT being sent through the
If on the other linux box I change the queue to laserjet 1100 so it
loads the right driver, then it works fine.
Fedora Core 1 is maintained by the Fedora Legacy project for security updates
only. If this problem is a security issue, please reopen and reassign to the
Fedora Legacy product. If it is not a security issue and hasn't been resolved in
the current FC5 updates or in the FC6 test release, reopen and change the
version to match.
NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy
project. After Fedora Core 6 Test 2 is released (currently scheduled for July
26th), there will be no more security updates for FC1. Please use these next two
weeks to upgrade any remaining FC1 systems to a current release.
Closed per above message and lack of response. Note that FC1 and FC2 are not even
supported by Fedora Legacy anymore.