Bug 141163 - No match for USB device: mfr "Samsung" model "ML-1710"
No match for USB device: mfr "Samsung" model "ML-1710"
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: foomatic (Show other bugs)
3
All Linux
medium Severity low
: ---
: ---
Assigned To: Tim Waugh
: EasyFix
: 145633 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-29 13:35 EST by Lauri Nurmi
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-30 13:16:52 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)
/usr/share/foomatic/db/source/printer/Samsung-ML-1710.xml (2.33 KB, text/plain)
2004-11-30 06:48 EST, Tim Waugh
no flags Details

  None (edit)
Description Lauri Nurmi 2004-11-29 13:35:53 EST
Description of problem:

[root@localhost tmp]# system-config-printer
No match for USB device:
  mfr "Samsung"
  model "ML-1710"
  desc ""
  cmdset "GDI"
Please report this message in Bugzilla:
  https://bugzilla.redhat.com/bugzilla
Choose 'foomatic' as the component.
Guessing ID Samsung-ML-1710 for match

... Which was the correct guess.

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

foomatic-3.0.2-3
Comment 1 Tim Waugh 2004-11-30 06:48:19 EST
Created attachment 107617 [details]
/usr/share/foomatic/db/source/printer/Samsung-ML-1710.xml

Please save this attachment and copy it to:

  /usr/share/foomatic/db/source/printer/Samsung-ML-1710.xml

Does this cause the correct model to be automatically selected?
Comment 2 Lauri Nurmi 2004-11-30 13:02:51 EST
Yes, the printer is now automatically selected without the warning when the
attached file is in use.
Good.
Comment 3 Tim Waugh 2004-11-30 13:16:52 EST
Great.
Comment 4 Tim Waugh 2005-01-20 06:05:05 EST
*** Bug 145633 has been marked as a duplicate of this bug. ***

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