Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 155126 - Recommended driver for Samsung ML-1750 gives error
Summary: Recommended driver for Samsung ML-1750 gives error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: foomatic
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-04-16 18:05 UTC by Gerry Tool
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-20 01:44:56 UTC


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.