Xsane can't see my scanner as user bobg, as root is detected.
bobg]# scanimage -L device `genesys:libusb:001:006' is a Canon LiDE 110 flatbed scanner
[bobg@Workstation-1 ~]$ lsusb Bus 001 Device 006: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
$ sane-find-scanner could not open USB device 0x04a9/0x1909 at 001:006: Access denied (insufficient permissions)
I have no idea what permissions need fixing. Xsane was installed as su root and I tried reinstall from sudo from bobg, that made no difference. I rarely need the scanner and today when I do it wont work in Fedora 31 updated today.
What have I done wrong?
Bob
On 4/9/20 2:11 PM, Bob Goodwin wrote:
Xsane can't see my scanner as user bobg, as root is detected.
bobg]# scanimage -L device `genesys:libusb:001:006' is a Canon LiDE 110 flatbed scanner
[bobg@Workstation-1 ~]$ lsusb Bus 001 Device 006: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
$ sane-find-scanner could not open USB device 0x04a9/0x1909 at 001:006: Access denied (insufficient permissions)
I have no idea what permissions need fixing. Xsane was installed as su root and I tried reinstall from sudo from bobg, that made no difference. I rarely need the scanner and today when I do it wont work in Fedora 31 updated today.
It seems that udev is not recognizing it or you need to add yourself to a different group. You could run xsane as root as a workaround. Or try doing "chmod a+w /dev/bus/001/006" (replace with the correct numbers if you've replugged or rebooted since your post).
P.S. Why do your emails always have a dash added at the end of the subject line?
On 2020-04-09 18:16, Samuel Sieb wrote:
It seems that udev is not recognizing it or you need to add yourself to a different group.
. i don't know what group?
You could run xsane as root as a workaround.
. Did that earlier, it warned me not to run as root and the did not let me save to Desktop, perhaps I should have tried saving to a root directory ... The urgency has passed, another scanner was coaxed into working with an Apple something. Now I just want to fix it since it has always worked from new, put aside for a year while a new floor was installed, until today when we needed it.
Or try doing "chmod a+w /dev/bus/001/006" (replace with the correct numbers if you've replugged or rebooted since your post).
. After some trial and error I wound up doing chmod 775 /dev/bus/usb but stilt not detected.
It used to be we had the GUI for users and groups and I would have looked there for a likely fix, that will be missed along with Alacarte which I could use to replace some of the cryptic names in the menu.
There's no good reason for the dash, just I've always done that, another eccentric user.
On 4/9/20 4:48 PM, Bob Goodwin wrote:
On 2020-04-09 18:16, Samuel Sieb wrote:
Or try doing "chmod a+w /dev/bus/001/006" (replace with the correct numbers if you've replugged or rebooted since your post).
. After some trial and error I wound up doing chmod 775 /dev/bus/usb but stilt not detected.
That only changes the permissions on the top-level directory. It won't affect the device files. The numbers correspond to the info you got from lsusb.
Bus 001 Device 006: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
/dev/bus/usb/001/006 is the device name.
On 2020-04-09 21:25, Samuel Sieb wrote:
/dev/bus/usb/001/006 is the device name.
°
[root@Workstation-1 bobg]# ls -al /dev/bus/usb/001/006 crw-rw-r--. 1 root root 189, 5 Apr 9 20:11 /dev/bus/usb/001/006
[root@Workstation-1 bobg]# chmod 777 /dev/bus/usb/001/006
[root@Workstation-1 bobg]# ls -al /dev/bus/usb/001/006 crwxrwxrwx. 1 root root 189, 5 Apr 9 20:11 /dev/bus/usb/001/006
That was what it needed, the permissions now are probably overkill, but it scans and saves.
Thank you for the help Sam.
-
Bob Goodwin -
Samuel Sieb