← Back to team overview

documentation-packages team mailing list archive

[Bug 663226] Re: "ScanningHowTo" page doesn't explain how to manually add a scanner which is supported by a driver, but undetected


Hi Dave, and thanks for your report!

Please note that anybody can edit the wiki page which John linked to.
Since you seem to know how it should be changed, it would be great if you could fix it.

Due to the nature of the community help wiki, you can't request changes
to it in the form of bug reports.

** Changed in: ubuntu-docs (Ubuntu)
       Status: Confirmed => Invalid

You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.

  "ScanningHowTo" page doesn't explain how to manually add a scanner
  which is supported by a driver, but undetected

Status in “ubuntu-docs” package in Ubuntu:

Bug description:
  Binary package hint: ubuntu-docs

  The Scanning page:
  https://help.ubuntu.com/10.04/printing/C/scanning.html has improved
  over the past few releases, but still was not helpful for me in
  solving this problem, which a quick search of the forums shows is
  quite common:

  1. No scanner detected
  2. Visit http://www.sane-project.org/sane-backends.html and find that the scanner is listed as well supported (in my case, the scanner is an Epson Stylus Office BX300F printer/scanner/fax, supported by the epson2 driver: http://www.sane-project.org/lists/sane-mfgs-cvs.html#Z-EPSON):
  Stylus Office BX300F 	USB 	0x04b8/0x0848 	Good 	all-in-one
  3. Ensure that the device ID is being claimed by the correct driver: Edit /etc/sane.d/epson2.conf and add the line:
  usb 0x4b8 0x848
  4. Ensure that the USB node's permissions are correctly set to allow unprivileged users to scan: add the following lines to /lib/udev/rules.d/40-libsane.rules:
  #Epson Office BX300F
  ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0848", ENV{libsane_matched}="yes"

  These four steps seem to be required for a large number of printers -
  it might be worth including them in the official docs.


To manage notifications about this bug go to: