В Tue, 07 Sep 2021 18:18:52 +0200
Jörg Frings-Fürst <debian@jff.email> пишет:

> Hello,
> 
> at first please answer always into the bug,too.
> 
> 
> First please send the output of
> 
> systemctl status udev

$ systemctl status udev
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: active (running) since Wed 2021-09-08 19:19:28 +07; 2s left
TriggeredBy: ● systemd-udevd-kernel.socket
             ● systemd-udevd-control.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
   Main PID: 277 (systemd-udevd)
     Status: "Processing with 24 children at max"
      Tasks: 1
     Memory: 36.6M
        CPU: 1.261s
     CGroup: /system.slice/systemd-udevd.service
             └─277 /lib/systemd/systemd-udevd

Warning: some journal files were not opened due to insufficient
permissions.

# systemctl status udev
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: active (running) since Wed 2021-09-08 19:19:28 +07; 38s ago
TriggeredBy: ● systemd-udevd-kernel.socket
             ● systemd-udevd-control.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
   Main PID: 277 (systemd-udevd)
     Status: "Processing with 24 children at max"
      Tasks: 1
     Memory: 36.6M
        CPU: 1.261s
     CGroup: /system.slice/systemd-udevd.service
             └─277 /lib/systemd/systemd-udevd
...






> Then check that
> 
> ENV{DEVNAME}!="", ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m
> g:scanner:rw $env{DEVNAME}"
> 
> is in one line without linebreak before the end.
 
OK

> 
> Next please test:
> 
> Add the file as root:
> 
> /etc/udev/rules.d/scanner.rules
> 
> 
> Insert this line 
> 
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="07b3", ATTRS{idProduct}=="1300",
> GROUP="scanner"
 

OK
 
 
> Then reboot und test it again.

Scanner detected!


$ 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 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 0x046d/0xc33a at 001:004: Access denied (insufficient
permissions) could not open USB device 0x062a/0x4101 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) could not open USB device 0x1d6b/0x0003 at
004:001: Access denied (insufficient permissions) found USB scanner
(vendor=0x07b3 [PLUSTEK INC], product=0x1300 [USB2.0 SCANNER],
chip=GL845) at libusb:003:002 could not open USB device 0x1d6b/0x0002
at 003:001: Access denied (insufficient permissions) # Your USB scanner
was (probably) detected. It may or may not be supported by # SANE. Try
scanimage -L and read the backend's manpage.

  
# 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.

found USB scanner (vendor=0x07b3 [PLUSTEK INC], product=0x1300 [USB2.0
SCANNER], chip=GL845) at libusb:003:002 # Your USB scanner was
(probably) detected. It may or may not be supported by # SANE. Try
scanimage -L and read the backend's manpage.

             


 
> If fails then give me the output of
> 
> systemctl status udev
> 
> again.


It works!


 $ systemctl status udev
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: active (running) since Wed 2021-09-08 19:28:35 +07; 22s ago
TriggeredBy: ● systemd-udevd-control.socket
             ● systemd-udevd-kernel.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
   Main PID: 280 (systemd-udevd)
     Status: "Processing with 24 children at max"
      Tasks: 1
     Memory: 36.9M
        CPU: 1.536s
     CGroup: /system.slice/systemd-udevd.service
             └─280 /lib/systemd/systemd-udevd

Warning: some journal files were not opened due to insufficient
permissions.


# systemctl status udev
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: active (running) since Wed 2021-09-08 19:28:35 +07; 2min
10s left TriggeredBy: ● systemd-udevd-control.socket
             ● systemd-udevd-kernel.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
   Main PID: 280 (systemd-udevd)
     Status: "Processing with 24 children at max"
      Tasks: 1
     Memory: 36.0M
        CPU: 1.573s
     CGroup: /system.slice/systemd-udevd.service
             └─280 /lib/systemd/systemd-udevd
...


Many thanks, Jörg !

WBR,
Andrei

Reply via email to