Bug 181295 - No match for USB device EPSON Stylus C62
No match for USB device EPSON Stylus C62
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: foomatic (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
:
Depends On:
Blocks: FC5Target
  Show dependency treegraph
 
Reported: 2006-02-12 19:35 EST by Christopher Beland
Modified: 2008-06-28 23:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-05 17:34:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
/usr/share/printconf/util/printconf_conf.py (61.37 KB, text/plain)
2006-02-14 07:38 EST, Tim Waugh
no flags Details

  None (edit)
Description Christopher Beland 2006-02-12 19:35:07 EST
* Description of problem:

After editing a print queue in system-config-printer, but not actually changing
anything, I got the following error message:

No match for USB device:
  mfr "EPSON"
  model "Stylus C62"
  desc "EPSON Stylus C62"
  cmdset "ESCPL2,BDC,D4"
Please report this message in Bugzilla

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

foomatic-3.0.2-19.2.i386.rpm
Comment 1 Tim Waugh 2006-02-13 06:31:15 EST
Thanks for the report.  Did it also say 'Guessing ID ... for match' after that?
Comment 2 Christopher Beland 2006-02-13 07:47:11 EST
Not that I noticed at the time.
Comment 3 Tim Waugh 2006-02-13 07:59:29 EST
Is it possible for you to try again?  Just clicking 'New' ought to be sufficient
to cause the message to be displayed.
Comment 4 Tim Waugh 2006-02-14 07:38:10 EST
Created attachment 124612 [details]
/usr/share/printconf/util/printconf_conf.py

Please save this attachment and copy it to:

  /usr/share/printconf/util/printconf_conf.py

Is the correct model now automatically selected from the list when you create a
new queue?  What is the output on the terminal now?
Comment 5 John Thacker 2006-05-05 17:34:47 EDT
Closing due to lack of response by reporter.
Comment 6 Christopher Beland 2008-06-28 23:30:06 EDT
Sorry, I no longer own this printer.

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