Bug 169121 - Select Generic PostScript model for unknown PS-capable printers
Select Generic PostScript model for unknown PS-capable printers
Status: CLOSED DEFERRED
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: foomatic (Show other bugs)
4.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
:
Depends On:
Blocks: FC5Target
  Show dependency treegraph
 
Reported: 2005-09-23 08:24 EDT by Peter Odufona
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-11-10 10:08:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Odufona 2005-09-23 08:24:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Description of problem:
Description of Problem:

ref: Bug 139218

I have an Oki B4350 printer. system-config-printer produces the following message on startup:

No match for USB device:
mfr "OKI DATA CORP"
model "B4350"
desc "OKI B4350"
cmdset "PJL,PCL,IBMPPR,EPSONFX,POSTSCRIPT,PCLXL"


and also...

No match for USB device:
mfr "Star"
model "TSP 700 (STR_T-U001)"
desc ""
cmdset "STAR"

Thanks


Version-Release number of selected component (if applicable):
kernel-smp-2.6.9-11,  system-config-printer-0.6.116-1

How reproducible:
Didn't try


Additional info:
Comment 1 Tim Waugh 2005-09-23 09:02:38 EDT
I think there should be more lines to the output.  Does the full output for this
one:

No match for USB device:
mfr "OKI DATA CORP"
model "B4350"
desc "OKI B4350"
cmdset "PJL,PCL,IBMPPR,EPSONFX,POSTSCRIPT,PCLXL"

say that it will choose Generic PostScript as the model? (And does it indeed do
that when you go to create a new queue for it?)

(Neither of these printers are listed in the foomatic database.)
Comment 2 Peter Odufona 2005-09-23 09:08:08 EDT
Apologies!

Beneath the "Please report this message to Bugzilla" line for both types of
printer, it reads...

Choose 'foomatic' as the component.

Hope this helps!

Rgds.
Comment 3 Tim Waugh 2005-09-23 09:09:36 EDT
When you go to create a new queue for that printer, is 'Generic PostScript'
selected automatically in the model list?
Comment 4 Peter Odufona 2005-09-23 09:30:47 EDT
No.

At the the printer model selection screen it defaults to :

Generic (click to select manufacturer), but none selected automatically or
highlighted.

queue type = Locally-connected
Comment 5 Tim Waugh 2005-09-23 11:47:03 EDT
Ah, okay, it only does what I expected it to for printers discovered using SNMP.
 It should do that for locally-connected printers as well.
Comment 6 Malcolm 2005-09-26 11:40:03 EDT
Tim, 

let me know who things are going, will be onsite with Specsavers on Wednesday,
as they have a support account, will run an Issue Tracker escalation as well....

Malcolm
Comment 7 Tim Waugh 2005-09-26 12:00:15 EDT
Just to clarify, I'm taking this bug report to be that PostScript-capable
printers are not automatically detected as "Generic PostScript", meaning that
the user has to manually select that.

Fixing this will not enable printing in a situation where printing is not
working.  Specifically, if there is a driver missing (for the Star printer?),
that is a much bigger job to rectify (and not normally something we'd do via
Bugzilla).

We will not make an update available for the Generic PostScript auto-selection
feature, since the easy work-around is to select "Generic PostScript" from the list.
Comment 8 Tim Waugh 2005-11-10 10:08:53 EST
Fixed in rawhide package system-config-printer-0.6.145-1.  The fix will be
included in a future release of Red Hat Enterprise Linux.

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