Bug 182169 - no print output on HP LaserJet 5M PostScript
Summary: no print output on HP LaserJet 5M PostScript
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-20 21:09 UTC by Bernd Bartmann
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2006-12-15 12:02:34 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bernd Bartmann 2006-02-20 21:09:20 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20060202 Fedora/1.0.7-1.2.fc4 Firefox/1.0.7

Description of problem:
On a freshly installed FC5T3 I tried to setup an HP LaserJet 5M generic PostScript printer via JetDirect. I named the print queue HP_LJ5M_PS. When trying to print any test page the display on the printer shortly display "Getting data" and then nothing happens, i.e. no page is printed. I remember having reported this problem back for nearly every FC release, then it got fixed but now it's back again.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. setup a PostScript print queue via JetDirect to a HP LaserJet 5M
2.
3.
  

Additional info:
Comment 1 Tim Waugh 2006-02-22 11:07:13 UTC 
How about if you set the 'Ghostscript Pre-Filtering' option to different values?
Comment 2 Bernd Bartmann 2006-02-23 17:15:37 UTC 
I've tried all four available options but none of them works.
Comment 3 Aaron Holtzman 2006-03-11 14:57:05 UTC 
I've had my Laserjet 5M broken since FC4 as well. Today I managed to get it to work by switching the drier 
to hpijs from Postscript (whatever that means).
Comment 4 Tim Waugh 2006-12-15 12:02:34 UTC 
The recommended driver for this device has been changed to PostScript.
Note You need to log in before you can comment on or make changes to this bug.