I'm currently helping out someone to replace Windows XP with OpenSuse 13.1. Most things work out pretty ok, but the scanner is giving me headaches. It is an old HP Scanjet 5370C which according to the lists on the SANE website is supported "good" for several years already.

I have been trying the directions given on https://en.opensuse.org/SDB:Configuring_Scanners but things have not worked out (yet).
When connecting the scanner lsusb does give the correct info:
Code:
Bus 004 Device 002: ID 056a:00de Wacom Co., Ltd 
Bus 006 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 012 Device 002: ID 03f0:0701 Hewlett-Packard ScanJet 5300c/5370c
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 012 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Running sane-find-scanner does not "detect" the scanner. When I run it as normal user I get a lot of
"could not open USB device 0x1d6b/0x0001 at 012:001: Access denied (insufficient permissions)"
errors:

Code:
  # 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 0x056a/0x00de at 004:002: Access denied (insufficient permissions)
could not open USB device 0x046d/0xc00e at 006:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 005:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 006:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 007:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 008:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 009:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 010:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 011:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 012: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.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.
Running it as root avoids the permission problems but the scanner is not detected. What I found suspicious is that while lsusb reports the device to be connected at "Bus 012 Device 002", this bus does not appear in the output list (maybe just because it doesn't trigger an error message?).

Also when going through the logs (dmesg | grep -i usb)I came across several messages like
Code:
usb 12-2: usbfs: interface 0 claimed by usbfs while 'saned' sets config #1
This makes me wonder whether there is a problem with the permissions for some usb devices. If this is true it may be easy to fix but I have no clue how.... All suggestions are more than welcome