Bug 155126

Summary:	Recommended driver for Samsung ML-1750 gives error
Product:	[Fedora] Fedora	Reporter:	Gerry Tool <gerry>
Component:	foomatic	Assignee:	Tim Waugh <twaugh>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-04-20 01:44:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gerry Tool 2005-04-16 18:05:35 UTC

Description of problem:The recommended pxlmono driver for this printer gives an
error printout instead of the docuement.  The alternate hpijs driver prints OK,
but doesn't have the same facilities.  The error printout is:

PCL6 ERROR - sfLxy_BitmapResRatio.x == sfLxy_BitmapResRatio.y
   POSITION : 0x4e4 (1252)
   SYSTEM   : GP/xl_dnloadfont
   LINE     : 400
   VERSION  : PCL6 3.12 01-03-2003




Version-Release number of selected component (if applicable):
foomatic-3.0.2-18, system-config-printer-0.6.128-1, cups-1.1.23-15

How reproducible:
Always

Steps to Reproduce:
1.Set up Samsung ML-1750 Laser printer on networked LPD server using rcommended
pxlmono driver
2.Print a document
3.
  
Actual results:
Error listed above is printed.

Expected results:
Document should be printed.

Additional info: I'm not sure foomatic is the correct component to charge with
this error.

Comment 1 Tim Waugh 2005-04-19 16:55:01 UTC

No idea what that error means. :-/

I can get foomatic to choose hpijs by default instead, but then we lose
functionality I suppose.

Comment 2 Gerry Tool 2005-04-20 01:44:56 UTC

I just tried a retest, and conclude that either my system was borked at the time
I reported the bug, or changing from Firefox 1.0.2 to 1.0.3 has fixed the
problem I had printing when I made the bug report.

I did earlier experience the same problem with Suse9.2 and "fixed" it there by
changing the driver as noted in the bug report.

So, close this as NOTABUG.  I apologize for the false alarm.