[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Scanner rights messed up: please help!



Christof Hurschler wrote:
Von: M-L <rose_snug@bigpond.com>
On Thursday 24 August 2006 19:10, Christof Hurschler shared this with us
all:
--> No one responded to my last post, so I'll try it again.  A previously
working scanner is no longer accessible for the group "scanner".  It
works
under root.  Something seems to have changed in a recent dist-upgrade.
-->
--> The device is listed as:
-->
--> T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
--> D:  Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
--> P:  Vendor=04b8 ProdID=0109 Rev= 1.07
--> S:  Manufacturer=EPSON
--> S:  Product=Expression1640XL
--> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  2mA
--> I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
--> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
--> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
-->
--> but ls -la /proc/bus/usb/001
--> total 0
--> dr-xr-xr-x 2 root root  0 2006-08-24 11:35 .
--> drwxr-xr-x 6 root root  0 2006-08-24 11:35 ..
--> -rw-r--r-- 1 root root 43 2006-08-24 11:35 001
--> -rw-r--r-- 1 root root 50 2006-08-24 09:36 002
-->
--> where 001:002 used to be root:scanner, allowing scanning by users in
that group.  Not any more. -->
--> I don't know where the rights for this device are beging set, can
someone suggest a way to solve this problem?  I did find someting about
setting rights in the documentation for usblib, but have never had to
intervene in this regard before.  And am not sure if that is the problem
anyway. -->
--> This is the second or thrid time that dist-upgrade has broken my
system
because of a rights problem.  First cups, more recently automounting in
KDE, and now the scanner problem.  I really like debian, but when
printing
or scanning or access to a usb stick suddenly stops working my debian
system becomes useless to me. -->
--> Chris
I was going to respond to your last post, but didn't really have anything
much to suggest.
1. a reboot
2. reinforcing that the user is added to the scanner group.

Thanks for your suggestion Charlie, but the user and group of the device are no longer being set to root:scanner anymore for some reason but to root:root.  In that case it doesnt matter if the user is in the sacnner group: it does't have any access to the device anyway....  Rebooting and crossing my fingers didn't change this situation ;-)

It can't be too difficult of a problem because root can scan fine using kooka.

Chris
I use sid and AKAICT udev deals with permissions for devices. Try /etc/udev/permission.rules.

HTH

Wackojacko



Reply to: