Bug 1251295

Summary: sane-find-scanner fails with Access denied (insufficient permissions)
Product: [Fedora] Fedora Reporter: Leek Soup <nerdgal7501>
Component: sane-backendsAssignee: Nils Philippsen <nphilipp>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 22CC: nphilipp
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 19:54:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Leek Soup 2015-08-06 23:25:36 UTC
Description of problem:
Attempting to get my Canon ImageFormula P-150 scanner to work on new install of Fedora 22. xsane does not find the scanner, so I tried sane-find-scanner and  it fails with Access denied errors. scanimage -L also fails, I am guessing scanimage and xsane fail (silently) because of same problem.

Version-Release number of selected component (if applicable):
sane-backends-1.0.24-14.fc22.i686

How reproducible:
happens every time

Steps to Reproduce:
1. connect scanner via USB and turn it on
2. sane-find-scanner

Actual results:
$ sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not open USB device 0x1083/0x162c at 002:021: Access denied (insufficient permissions)
could not open USB device 0x18e3/0x9102 at 002:003: Access denied (insufficient permissions)
could not open USB device 0x8087/0x0020 at 002:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions)
could not open USB device 0x8087/0x0020 at 001:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
  # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

  # Not checking for parallel port scanners.
...


Expected results:
Finds scanner.


Additional info:
sane-find-scanner, scanimage, and xsane all worked with the same scanner on F12 - F17. I just checked an old F12 machine and the permissions on /dev/bus/usb/*/* are the same as on the new system, yet cause no problems to scanning.

If I sudo and change permissions to world write for that USB connection, sane-find-scanner does work. This has to be done every time the scanner is plugged.

$ sudo chmod 666 /dev/bus/usb/002/021
[sudo] password for leeksoup:
$ sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x1083, product=0x162c) at libusb:002:021
...

Comment 1 Fedora End Of Life 2016-07-19 19:54:55 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.