You are not logged in.
Pages: 1
Topic closed
When I'm logged in as a normal user, scanimage -L doesn't work (No scanners were identified. If you were blablabla...). sane-find-scanner display the right information about my scanner.
It seems that I have the same model as the one in the wiki :s
Minor remarks for some plustek scanners (noticeably Canoscan ones), they require a lock directory. Make sure that /var/lock/sane directory exists, that its permissions are 660, and that it is owned by root:scanner. If the directory permissions are wrong, only root will be able to use the scanner. Seems (at least on x86-64) that some programs using libusb (noticeably xsane and kooka) need scanner group rw permissions also for accessing /proc/bus/usb to work for a normal user.
I am a member of the scanner group (checked with "groups"),
/var/lock/sane folder exist, is owned by root.scanner :
drw-rw---- 2 root scanner 4096 2008-04-20 18:04 sane
I changed permissions for /proc/bus/usb/001/002 (where my scanner is) and the owner, but nothing to do, it doesn't want me to use my scanner as a simple user.
Few days ago I tested the last ubuntu release (hardy), xsane worked very well, the scanner was plugged in the same usb slot. So I'm sure it is configuration related.
Thank you for the help
Last edited by faelar (2008-04-20 16:56:15)
Offline
I have Canon Lide20, which seems to suffer from the same problem. The solution for me was to add a udev rule that looks like this:
$ cat /etc/udev/rules.d/96-scanner.rules
BUS=="usb", SYSFS{product}=="CanoScan", MODE="664", GROUP="scanner"
Your user has to be in the "scanner" group of course. Once you create the rule you'll have to unplug the scanner and plug it back in for it to take effect.
Offline
Your user has to be in the "scanner" group of course. Once you create the rule you'll have to unplug the scanner and plug it back in for it to take effect.
Sorry to hijack the thread, but don't you have to restart udev as well? (I mean, does udev read the rules dynamically?)
Offline
It is possible that I'm wrong, I'm not going to check right now, but I don't remember restarting udev last time I was setting this up -- though it was a while ago, admittedly...
Offline
@ bender02: yes it does (at least it should) I have a similar problem with my libmtp device that would not let me approach it as my own user, only as root... I ended up assigning it to my user.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Offline
I followed all instructions on the wiki article, and tried the udev rules. Nothing helped for my Lide20. In the end I figured that I had to change the owner of /var/lock/sane to <user>:scanner. With this change, I don't need udev rules, and it works flawlessly. I changed the wiki article accordingly.
Offline
I'd say udev rules are preferable over changing ownership by hand, but I guess in the end it's all personal preference.
Anyway - you're kicking a topic that's over 1,5 years old. We don't do necro-bumping over here .
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Pages: 1
Topic closed