Bug 156661 - foomatic not recognizing EPSON CX5400 correctly
foomatic not recognizing EPSON CX5400 correctly
Product: Fedora
Classification: Fedora
Component: foomatic (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2005-05-02 19:36 EDT by Richard Wilson
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 3.0.2-19
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-14 05:04:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/usr/share/foomatic/db/source/printer/Epson-Stylus_CX5400.xml (2.19 KB, text/plain)
2005-05-03 10:57 EDT, Tim Waugh
no flags Details

  None (edit)
Description Richard Wilson 2005-05-02 19:36:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Description of problem:
Version info:

root> printtool &
No match for USB device:
  mfr "EPSON"
  model "Stylus CX5400"
  desc "EPSON Stylus CX5400"
  cmdset "ESCPL2,BDC,D4"
Please report this message in Bugzilla:
Choose 'foomatic' as the component.

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

How reproducible:

Steps to Reproduce:
1. Start printtool (or system-config-printer)
2. remove the queue added by kudzu at system startup leaving my defined queue "epson"
3. Save the results

Actual Results:  Somewhere in the course of these steps, the "No match for USB device" message given above appears.

Expected Results:  no message.

Additional info:

This does not prevent the printer from working (haven't tested the scanning yet).  Wouldn't have bothered reporting this except it repeatedly asks me to do so.   I expect that it's receiving something unexpected from the printer.
Comment 1 Tim Waugh 2005-05-03 10:57:47 EDT
Created attachment 113965 [details]

Thanks for the report.	Please save this attachment and copy it to:


Does the warning message still appear?
Comment 2 Tim Waugh 2005-06-14 05:03:26 EDT
Comment 3 Richard Wilson 2005-06-14 10:39:24 EDT
The warning message no longer appears.  Thanks!

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