LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   udev and scanner - only as root since upgrade to -current (https://www.linuxquestions.org/questions/slackware-14/udev-and-scanner-only-as-root-since-upgrade-to-current-594071/)

niels.horn 10-23-2007 09:03 PM

udev and scanner - only as root since upgrade to -current
 
Hi to all,

I'm having this silly problem since I upgraded to -current a few days ago.
My scanner (Canon LiDE 20) is only working as root, not as any other user.

scanimage -L doesn't find my scanner as a normal user.

as root it returns:
Code:

device `plustek:libusb:002:004' is a Canon N670U/N676U/LiDE20 USB flatbed scanner
I checked the obvious: yes, I am a member of the group 'scanner'.

udev creates /dev/usbdev2.4 with owner=root, group=scanner, mode=660
But I found /dev/bus/usb/002/004 is root.root mode 644

When I do "chmod 666 /dev/bus/usb/002/004" it is recognized by any normal user and evrything works fine until my next boot.

I checked /etc/udev/rules.d/80-libsane.rules and there is a line saying:
Code:

SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="220d", MODE="660", GROUP="scanner"
Apparently everything here is ok, but there seems to be some problem at a lower level creating /dev/bus/usb/002/004

This all worked fine before upgrading to -current

Any ideas?

allend 10-24-2007 11:28 AM

I am having a similiar difficulty with my Brother DCP-110C printer/scanner.
As root, everything works just fine.
However, for a normal user (who is a member of the scanner group) to access the scanner, I have found that I need to execute 'chgrp scanner /dev/bus/usb/xxx/yyy' where xxx is the Bus number and yyy is the device number reported by 'lsusb'.
It appears that an alteration to the udev rules is required (maybe in 65-permissions.rules or else by creation of 90-local.rules), but I do not have a solution at this time.

rworkman 10-24-2007 01:02 PM

Run this and post all output.
This is probably something missing in the 80-libsane.rules (perhaps they haven't caught up to changes in latest udev)
Code:

udevinfo --query=all --attribute-walk --name /dev/bus/usb/002/004

Piter PUNK 10-24-2007 01:14 PM

Hi,

Can you make available a tar.gz from your /dev and your /etc/udev?
this is important to me to see and discover what is happening.
If you can send your /etc/group is good, too.

Thanks

Piter PUNK

niels.horn 10-24-2007 02:19 PM

Well, Robby Workman and Piter PUNK replying to my thread... I'm honored! :cool:

udevinfo --query=all --attribute-walk --name /dev/bus/usb/002/005 (after unplugging and plugging my scanner changed to 002/005) gives:

Code:

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:10.1/usb2/2-2':
    KERNEL=="2-2"
    SUBSYSTEM=="usb"
    DRIVER=="usb"
    ATTR{product}=="CanoScan"
    ATTR{manufacturer}=="Canon"
    ATTR{quirks}=="0x1"
    ATTR{maxchild}=="0"
    ATTR{version}==" 1.10"
    ATTR{devnum}=="5"
    ATTR{busnum}=="2"
    ATTR{speed}=="12"
    ATTR{bMaxPacketSize0}=="8"
    ATTR{bNumConfigurations}=="1"
    ATTR{bDeviceProtocol}=="ff"
    ATTR{bDeviceSubClass}=="00"
    ATTR{bDeviceClass}=="ff"
    ATTR{bcdDevice}=="0100"
    ATTR{idProduct}=="220d"
    ATTR{idVendor}=="04a9"
    ATTR{bMaxPower}=="500mA"
    ATTR{bmAttributes}=="a0"
    ATTR{bConfigurationValue}=="1"
    ATTR{bNumInterfaces}==" 1"
    ATTR{configuration}==""
    ATTR{dev}=="189:132"

  looking at parent device '/devices/pci0000:00/0000:00:10.1/usb2':
    KERNELS=="usb2"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{serial}=="0000:00:10.1"
    ATTRS{product}=="UHCI Host Controller"
    ATTRS{manufacturer}=="Linux 2.6.23.1-smp uhci_hcd"
    ATTRS{quirks}=="0x0"
    ATTRS{maxchild}=="2"
    ATTRS{version}==" 1.10"
    ATTRS{devnum}=="1"
    ATTRS{busnum}=="2"
    ATTRS{speed}=="12"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bcdDevice}=="0206"
    ATTRS{idProduct}=="0000"
    ATTRS{idVendor}=="0000"
    ATTRS{bMaxPower}=="  0mA"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{configuration}==""
    ATTRS{dev}=="189:128"

  looking at parent device '/devices/pci0000:00/0000:00:10.1':
    KERNELS=="0000:00:10.1"
    SUBSYSTEMS=="pci"
    DRIVERS=="uhci_hcd"
    ATTRS{msi_bus}==""
    ATTRS{broken_parity_status}=="0"
    ATTRS{enable}=="1"
    ATTRS{modalias}=="pci:v00001106d00003038sv00001106sd00003038bc0Csc03i00"
    ATTRS{local_cpus}=="ffffffff"
    ATTRS{irq}=="18"
    ATTRS{class}=="0x0c0300"
    ATTRS{subsystem_device}=="0x3038"
    ATTRS{subsystem_vendor}=="0x1106"
    ATTRS{device}=="0x3038"
    ATTRS{vendor}=="0x1106"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""
    ATTRS{uevent}==""

To Piter:
Quote:

Can you make available a tar.gz from your /dev and your /etc/udev?
this is important to me to see and discover what is happening.
If you can send your /etc/group is good, too.
I can send it to an e-mail address if you want (the one that is in the man page of slackpkg?)

Hopefully we can find a solution! :scratch:

Edit:
I just found that changing this line:
Code:

SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"
in 50-udev-default.rules to:
Code:

SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0666"
(changing 0644 to 0666) "resolves" my problem.
But is it supposed to work this way? Now I am giving rw access to everybody...

anewguy 10-25-2007 01:59 AM

Similar problem?
 
I am a newbie, so please forgive me if I am misunderstanding this. If I am following correctly, the USB device(s) are getting mounted with root access only?

I ask this because I am using the avidownload program from sourceforge to download videos off a hacked 1-time use CVS video camera. If I don't run the application as root, it won't open the device. This all uses libusb.

Because it downloads videos to a directory in the users' directory tree, the user now ends up with files he can't delete, etc., because they are owned by root.

Does this sound like a similar problem (I thought it did)?

BTW - I'm running Ubuntu 7.10. Can you point me to the place where I would make the above change?

Thanks!
Dave

EDIT: SOLVED - yes!, this was the problem. In Ubuntu I had to edit /etc/udev/rules.d/40-permissions.rules. Works like a champ! Thanks, guys!!

Fluxx 10-25-2007 02:28 AM

Hi niels.horn,

quite good! This is also the solution for my camera in current udev!

http://www.linuxquestions.org/questi...-gtkam-594315/

Thank you very much!

Fluxx.

niels.horn 10-25-2007 04:34 AM

Solved or hacked?
 
Quote:

Originally Posted by anewguy
SOLVED - yes!, this was the problem.

Quote:

Originally Posted by Fluxx
quite good! This is also the solution for my camera in current udev!

Well, at least I made some people happy. :D
But I'm not very proud of my solution, it's more like a hack.

Maybe the real experts can give their opinion here about my preoccupation with the security consequences of giving r/w access to a device to everyone.
I know that in a home environment this won't be a problem, but in an office it might be. (In my office I only have read access to the usb ports so that I cannot copy documents to my pendrive)
I thought of changing the rule to give access only to a group called 'usb' (I'd have to create it) with
Code:

MODE="660", GROUP="usb"
in the default-rules line. Then to use the scanner I have to be a member of 'scanner' and 'usb'.

What do you think?

rworkman 10-25-2007 10:20 AM

Please still send the requested information - mail it to PiterPunk (piterpunk@) and CC me (rworkman@)

niels.horn 10-25-2007 10:56 AM

Ok, I'll send the information tonight from home. I agree with your comment in the other thread that what I did is not the ideal solution, just a workaround so that I donīt have to do a chmod everytime I plug in my scanner or reboot.

rworkman 10-25-2007 11:10 AM

For the time being, this *should* work for you - put this in a 90-local.rules file:
Code:

SUBSYSTEM=="usb" \
  ATTR{product}=="CanoScan" \
  ATTR{manufacturer}=="Canon" \
  GROUP:="plugdev" \
  MODE:="0664"

Please confirm whether or not this works.

allend 10-25-2007 11:28 AM

Thanks Robby,

I have just spent a lot of time finding that this works for me.
~$ cat /etc/udev/rules.d/90-local.rules
Code:

# Custom rule to assign privileges to scanner device file
SUBSYSTEM=="usb",  ATTR{idProduct}=="0169",  ATTR{idVendor}=="04f9",  ATTR{dev}=="189*" \
                  GROUP="scanner", MODE="0660"


Piter PUNK 10-25-2007 08:32 PM

Quote:

Originally Posted by allend (Post 2936557)
Code:

# Custom rule to assign privileges to scanner device file
SUBSYSTEM=="usb",  ATTR{idProduct}=="0169",  ATTR{idVendor}=="04f9",  ATTR{dev}=="189*" \
                  GROUP="scanner", MODE="0660"


Can you try the rules that are here?
http://slackware.com/~piterpunk/udev/testing

SYSFS attribute are marked to be obsolete some time ago. Use ATTR is the
preferred way (and now, the only correct way). Some rules shipped with other
packages doesn't fix it yet.

Piter PUNK

niels.horn 10-25-2007 10:13 PM

To Robby Workman:
Quote:

Please confirm whether or not this works.
Yes it does. Now the /dev/bus/usb/aaa/bbb is created with mode 664 group plugdev

I'll send the info in a few moments by e-mail.

Thanks for the help until now!

rworkman 10-25-2007 10:26 PM

Quote:

Originally Posted by niels.horn (Post 2937141)
To Robby Workman:

Yes it does. Now the /dev/bus/usb/aaa/bbb is created with mode 664 group plugdev

I'll send the info in a few moments by e-mail.

Thanks for the help until now!

Thank you. At this point, I don't think we need any more information.
We were exchanging random thoughts on IRC and suddenly there was a flash of light, and PiterPunk had the solution. ;-) See his post above.

allend 10-25-2007 10:38 PM

PiterPunk,

I will try the rules tonight after work.
It looks as though you have edited the files to use ATTR in place of SYSFS.
I did try commenting out the line for my Brother DCP-110C in 80-libsane.rules and replacing it with a line with ATTR in place of SYSFS, but I still needed to apply the custom rule to set the privileges.

niels.horn 10-25-2007 10:40 PM

ok, thanks Robby and Piter for your help!
I think we have a decent solution for this little problem now :-)

niels.horn 10-26-2007 07:19 AM

To Robby and Piter:
I forgot to mention that I changed the line just a little. Instead of:
Code:

GROUP:="plugdev" MODE:="0664"
I entered:
Code:

GROUP="plugdev" MODE="0664"
I had never seen the syntax using := so I imagined it might have been a typo.

Now a more generic doubt:
This works fine for my scanner. But what about any other equipment? If I buy another scanner / digital camera / whatever, do I need to add a new custom rule like this? Or is there a generic rule I can change?

rworkman 10-26-2007 08:12 AM

Quote:

Originally Posted by niels.horn (Post 2937506)
To Robby and Piter:
I forgot to mention that I changed the line just a little. Instead of:
Code:

GROUP:="plugdev" MODE:="0664"
I entered:
Code:

GROUP="plugdev" MODE="0664"
I had never seen the syntax using := so I imagined it might have been a typo.

That's valid syntax - it prevents the assigned values from being overridden by later rules.
I figured it probably wasn't necessary, but at the time, it couldn't hurt :)

Quote:

Now a more generic doubt:
This works fine for my scanner. But what about any other equipment? If I buy another scanner / digital camera / whatever, do I need to add a new custom rule like this? Or is there a generic rule I can change?
Well, that depends. It appears that the sane, libgphoto2, and probably other upstream guys need to issue new releases with udev rules that work with current udev versions. As for what Pat will do until that happens, I don't know.

allend 10-26-2007 09:47 AM

Piter Punk,

Thanks for your involvement in this as well as all the good work you do to benefit us all!

To other readers, I apologise for the long post.

This is the results of the testing that I have done.

First- Output of lsusb and ls -l when /etc/udev/rules.d contains the defaults in Slackware current where my Brother DCP-110C scanner is not available to users other than root.
Quote:

~$ /sbin/lsusb
Bus 006 Device 001: ID 0000:0000
Bus 007 Device 004: ID 0424:2504 Standard Microsystems Corp.
Bus 007 Device 001: ID 0000:0000
Bus 005 Device 002: ID 04f9:0169 Brother Industries, Ltd
Bus 005 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 005: ID 413c:2105 Dell Computer Corp.
Bus 004 Device 004: ID 0461:4d15 Primax Electronics, Ltd
Bus 004 Device 001: ID 0000:0000
~$ ls -l /dev/usbdev5*
crw-rw---- 1 root root 189, 512 2007-10-27 10:11 /dev/usbdev5.1
crw-rw---- 1 root root 254, 8 2007-10-27 10:11 /dev/usbdev5.1_ep00
crw-rw---- 1 root root 254, 9 2007-10-27 10:11 /dev/usbdev5.1_ep81
crw-rw---- 1 root scanner 189, 513 2007-10-27 00:11 /dev/usbdev5.2
crw-rw---- 1 root root 254, 20 2007-10-27 00:11 /dev/usbdev5.2_ep00
crw-rw---- 1 root root 254, 21 2007-10-27 00:11 /dev/usbdev5.2_ep01
crw-rw---- 1 root root 254, 23 2007-10-27 00:11 /dev/usbdev5.2_ep03
crw-rw---- 1 root root 254, 26 2007-10-27 00:11 /dev/usbdev5.2_ep08
crw-rw---- 1 root root 254, 22 2007-10-27 00:11 /dev/usbdev5.2_ep82
crw-rw---- 1 root root 254, 24 2007-10-27 00:11 /dev/usbdev5.2_ep84
crw-rw---- 1 root root 254, 25 2007-10-27 00:11 /dev/usbdev5.2_ep85
crw-rw---- 1 root root 254, 27 2007-10-27 00:11 /dev/usbdev5.2_ep89
~$ ls -l /dev/bus/usb/005
total 0
crw-r--r-- 1 root root 189, 512 2007-10-27 10:11 001
crw-r--r-- 1 root root 189, 513 2007-10-27 00:11 002
Second- Output of lsusb and ls -l when /etc/udev/rules.d contains the defaults in Slackware current _and_ the custom rule in 90-local.rules where my Brother DCP-110C scanner _is_ available to users other than root.
Quote:

~$ /sbin/lsusb
Bus 002 Device 001: ID 0000:0000
Bus 006 Device 003: ID 413c:2105 Dell Computer Corp.
Bus 006 Device 002: ID 0461:4d15 Primax Electronics, Ltd
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 007 Device 002: ID 04f9:0169 Brother Industries, Ltd
Bus 007 Device 001: ID 0000:0000
Bus 004 Device 004: ID 0424:2504 Standard Microsystems Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
~$ ls -l /dev/usbdev7*
crw-rw---- 1 root root 189, 768 2007-10-27 10:02 /dev/usbdev7.1
crw-rw---- 1 root root 254, 12 2007-10-27 10:02 /dev/usbdev7.1_ep00
crw-rw---- 1 root root 254, 13 2007-10-27 10:02 /dev/usbdev7.1_ep81
crw-rw---- 1 root scanner 189, 769 2007-10-27 00:02 /dev/usbdev7.2
crw-rw---- 1 root root 254, 20 2007-10-27 00:02 /dev/usbdev7.2_ep00
crw-rw---- 1 root root 254, 21 2007-10-27 00:02 /dev/usbdev7.2_ep01
crw-rw---- 1 root root 254, 23 2007-10-27 00:03 /dev/usbdev7.2_ep03
crw-rw---- 1 root root 254, 26 2007-10-27 00:02 /dev/usbdev7.2_ep08
crw-rw---- 1 root root 254, 22 2007-10-27 00:02 /dev/usbdev7.2_ep82
crw-rw---- 1 root root 254, 24 2007-10-27 00:03 /dev/usbdev7.2_ep84
crw-rw---- 1 root root 254, 25 2007-10-27 00:03 /dev/usbdev7.2_ep85
crw-rw---- 1 root root 254, 27 2007-10-27 00:02 /dev/usbdev7.2_ep89
~$ ls -l /dev/bus/usb/007
total 0
crw-r--r-- 1 root root 189, 768 2007-10-27 10:02 001
crw-rw---- 1 root scanner 189, 769 2007-10-27 00:03 002
Third- Output of lsusb and ls -l when /etc/udev/rules.d contains the defaults in Slackware current as well as your new rules where my Brother DCP-110C scanner is not available to users other than root.
Quote:

~$ /sbin/lsusb
Bus 007 Device 002: ID 04f9:0169 Brother Industries, Ltd
Bus 007 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 006 Device 003: ID 413c:2105 Dell Computer Corp.
Bus 006 Device 002: ID 0461:4d15 Primax Electronics, Ltd
Bus 006 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 004: ID 0424:2504 Standard Microsystems Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
~$ ls -l /dev/usbdev7*
crw-rw---- 1 root root 189, 768 2007-10-27 09:17 /dev/usbdev7.1
crw-rw---- 1 root root 253, 12 2007-10-27 09:17 /dev/usbdev7.1_ep00
crw-rw---- 1 root root 253, 15 2007-10-27 09:17 /dev/usbdev7.1_ep81
crw-rw---- 1 root root 189, 769 2007-10-26 23:17 /dev/usbdev7.2
crw-rw---- 1 root root 253, 20 2007-10-26 23:17 /dev/usbdev7.2_ep00
crw-rw---- 1 root root 253, 21 2007-10-26 23:17 /dev/usbdev7.2_ep01
crw-rw---- 1 root root 253, 23 2007-10-26 23:17 /dev/usbdev7.2_ep03
crw-rw---- 1 root root 253, 26 2007-10-26 23:17 /dev/usbdev7.2_ep08
crw-rw---- 1 root root 253, 22 2007-10-26 23:17 /dev/usbdev7.2_ep82
crw-rw---- 1 root root 253, 24 2007-10-26 23:17 /dev/usbdev7.2_ep84
crw-rw---- 1 root root 253, 25 2007-10-26 23:17 /dev/usbdev7.2_ep85
crw-rw---- 1 root root 253, 27 2007-10-26 23:17 /dev/usbdev7.2_ep89
~$ ls -l /dev/bus/usb/007/
total 0
crw-r--r-- 1 root root 189, 768 2007-10-27 09:17 001
crw-r--r-- 1 root root 189, 769 2007-10-26 23:17 002
Fourth- Output of lsusb and ls -l when /etc/udev/rules.d contains the defaults in Slackware current as well as your new rules _and_ the custom rule in 90-local.rules where my Brother DCP-110C scanner _is_ available to users other than root.
Quote:

~$ /sbin/lsusb
Bus 006 Device 001: ID 0000:0000
Bus 007 Device 004: ID 0424:2504 Standard Microsystems Corp.
Bus 007 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 005 Device 002: ID 04f9:0169 Brother Industries, Ltd
Bus 005 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 005: ID 413c:2105 Dell Computer Corp.
Bus 004 Device 004: ID 0461:4d15 Primax Electronics, Ltd
Bus 004 Device 001: ID 0000:0000
~$ ls -l /dev/usbdev5*
crw-rw---- 1 root root 189, 512 2007-10-27 09:38 /dev/usbdev5.1
crw-rw---- 1 root root 253, 8 2007-10-27 09:38 /dev/usbdev5.1_ep00
crw-rw---- 1 root root 253, 9 2007-10-27 09:38 /dev/usbdev5.1_ep81
crw-rw---- 1 root root 189, 513 2007-10-26 23:38 /dev/usbdev5.2
crw-rw---- 1 root root 253, 20 2007-10-26 23:38 /dev/usbdev5.2_ep00
crw-rw---- 1 root root 253, 21 2007-10-26 23:38 /dev/usbdev5.2_ep01
crw-rw---- 1 root root 253, 23 2007-10-26 23:40 /dev/usbdev5.2_ep03
crw-rw---- 1 root root 253, 26 2007-10-26 23:38 /dev/usbdev5.2_ep08
crw-rw---- 1 root root 253, 22 2007-10-26 23:38 /dev/usbdev5.2_ep82
crw-rw---- 1 root root 253, 24 2007-10-26 23:40 /dev/usbdev5.2_ep84
crw-rw---- 1 root root 253, 25 2007-10-26 23:40 /dev/usbdev5.2_ep85
crw-rw---- 1 root root 253, 27 2007-10-26 23:38 /dev/usbdev5.2_ep89
~$ ls -l /dev/bus/usb/005/
total 0
crw-r--r-- 1 root root 189, 512 2007-10-27 09:38 001
crw-rw---- 1 root scanner 189, 513 2007-10-26 23:40 002
In summary, the new rules work with my scanner (I cannot comment on the other rule sets as I have no way to test).
The change from SYSFS to ATTR does have have an effect on privileges at the /dev/usbdev* level, but the use of a custom rule allows the privileges to be set at the /dev/bus/usb/* level so that the scanner can be used by users other than root via programs such as scanimage, xsane and kooka.

shaney 11-25-2007 05:16 AM

I solved this problem changing in /etc/udev/rules.d/80-libsane.rules

Code:

SUBSYSTEM!="usb_device", GOTO="libsane_rules_end"
with

Code:

SUBSYSTEM!="usb", GOTO="libsane_rules_end"

BCarey 05-20-2008 06:17 PM

I am still having this problem. I have not yet replied to this post, because I had to role back to an older kernel due to my wireless card, and I was afraid that was why these solutions weren't working. Anyway, I've got the card working on 2.6.25, so I'd like to fix this problem now.

I have tried all the solutions mentioned here to no avail. The only thing here that changes my computer's behavior at all is Piter Punk's rules, which cause the /dev/usb* entry to show root group instead of scanner group.

One thing I notice is that you are all talking about /dev/bus/usb/xxx/yyy, but on my computer I do not have this directory, rather I have /proc/bus/usb/xxx/yyy. So do I have a misconfigured kernel? Everything else is stock slackware. This is not an upgrade from a prior Slack version (well, it is an upgrade from 12.1 rc1 or rc2).

Brian

digger95 05-21-2008 03:40 AM

Quote:

Originally Posted by BCarey (Post 3159626)
One thing I notice is that you are all talking about /dev/bus/usb/xxx/yyy, but on my computer I do not have this directory, rather I have /proc/bus/usb/xxx/yyy.

As a point of reference I have both on my machine. Sorry to hear you're still having problems. All I had to do was add my username to the 'scanner' group and my HP Scanjet (usb) worked out of the box.

gbloon 11-16-2008 11:04 AM

I just found this thread, while trying to get my scanner working as regular user, instead of only root.
Scanner is Canon LIDE25, OS is Slackware 12.1

I found the simple solution; just add your username to the scanner group. Open /etc/group, find the line that starts "scanner", and append your username to the end of the line (after a comma if you are not the only user in this group). Then logout, and log in again (or reboot).

Posting this in case it helps someone.


All times are GMT -5. The time now is 02:16 PM.