Servus zusammen,
ich habe seit etlichen Jahren einen Scanner, der unter Opensuse 13.2 und auch diversen Vorgänger-Distributionen von Suse/Opensuse problemlos lief. Es ist ein Mustek ScanExpress A3 USB.
Ich benutze ihn nicht oft, heute nach einigen Monaten mal wieder, und da konnte ich ihn nicht mehr ansprechen. Bzw., nach einigem Suchen, ich kann ihn als Benutzer root durchaus ansprechen und benutzen, aber nicht als Normalbenutzer. Das war zuvor nicht der Fall, vor einigen Monaten habe ich ihn unter 13.2 noch problemlos als Normalbenutzer benutzt.
lsusb:
Bus 002 Device 006: ID 2109:3431
Bus 002 Device 007: ID 0451:3410 Texas Instruments, Inc. TUSB3410 Microcontroller
Bus 002 Device 004: ID 043e:9a10 LG Electronics USA, Inc.
Bus 002 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 2109:0810
Bus 004 Device 002: ID 043e:9a11 LG Electronics USA, Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 017: ID 055f:0210 Mustek Systems, Inc. ScanExpress A3 USB
Bus 001 Device 006: ID 04f9:003d Brother Industries, Ltd
Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 003: ID 045e:0752 Microsoft Corp. Wired Keyboard 400
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Alles anzeigen
scanimage -L:
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
sudo scanimage-L:
device `gt68xx:libusb:001:017' is a Mustek ScanExpress A3 USB flatbed scanner
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 0x2109/0x3431 at 002:006: Access denied (insufficient permissions)
could not open USB device 0x0451/0x3410 at 002:007: Access denied (insufficient permissions)
could not open USB device 0x043e/0x9a10 at 002:004: Access denied (insufficient permissions)
could not open USB device 0x058f/0x6364 at 002:003: Access denied (insufficient permissions)
could not open USB device 0x8087/0x0024 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 0x2109/0x0810 at 004:003: Access denied (insufficient permissions)
could not open USB device 0x043e/0x9a11 at 004:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions)
could not open USB device 0x055f/0x0210 at 001:017: Access denied (insufficient permissions)
could not open USB device 0x04f9/0x003d at 001:006: Access denied (insufficient permissions)
could not open USB device 0x051d/0x0002 at 001:004: Access denied (insufficient permissions)
could not open USB device 0x045e/0x0752 at 001:003: Access denied (insufficient permissions)
could not open USB device 0x8087/0x0024 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.
# 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.
Alles anzeigen
sudo 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
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x0451, product=0x3410) at libusb:002:007
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x055f, product=0x0210 [USB Scanner], chip=GT-6816) at libusb:001:017
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
Alles anzeigen
YaST2 findet den Scanner ohne Probleme, richtet ihn ein, Test erfolgreich. Xsane als root (nach Hinweis, dass XSane als root zu benutzen "saugefährlich" ist): Scanner funktioniert problemlos. Xsane als Normalnutzer: Fehlermeldung "Keine Geräte erreichbar".
Was muss ich tun, um den Scanner wieder wie zuvor als Normalnutzer benutzen zu können?
