Hello, On Jun 13 16:55 Bob Kline wrote (shortened): > Johannes Meixner wrote: > > You may check the following: > > > > Note the USB IDs for vendor and model in the "lsusb" output. > > E.g. my Canon LiDE 30 is listed this way: > > --------------------------------------------------------------------- > > Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30 > > --------------------------------------------------------------------- > > Right -- different bus and device numbers, of course, but the > hardware ID is identical to yours. > > > Check if those USB IDs are in your > > /etc/hal/fdi/policy/10osvendor/70-scanner.fdi > > or at least in your > > /etc/hal/fdi/policy/10osvendor/80-scanner.fdi > > E.g. in my 70-scanner.fdi there is > > --------------------------------------------------------------------- > > <match key="info.category" string="usbraw"> > > <match key="@info.parent:usb_device.vendor_id" int="0x04a9"> > > <match key="@info.parent:usb_device.product_id" int="0x220e"> > > <append key="info.capabilities" type="strlist">scanner</append> > > </match> > > </match> > > </match> > > --------------------------------------------------------------------- > > OK, I've got that block in 70-scanner.fdi. > > > This way via udev and HAL the resmgr will be notified that > > this USB device is a scanner so that resmgr will set an > > appropriate ACL on its device file. > > That's the part that doesn't work on my system. So perhaps the presence > of my scanner in the .fdi file is necessary, but not sufficient. > > > Accordingly > > /usr/sbin/hal-resmgr --list > > shows my Canon LiDE 30 as > > ---------------------------------------------------------------------- > > UDI /org/freedesktop/Hal/devices/usb_device_4a9_220e_noserial_usbraw > > Device /dev/bus/usb/001/003 > > Class scanner > > ---------------------------------------------------------------------- > > That command's output is empty here. > > > and > > getfacl /dev/bus/usb/001/003 > > shows the actual ACL on the scanner's device file > > ---------------------------------------------------------------------- > > getfacl: Removing leading '/' from absolute path names > > # file: dev/bus/usb/001/003 > > # owner: root > > # group: root > > user::rw- > > user:jsmeix:rw- > > group::r-- > > mask::rw- > > other::r-- > > ---------------------------------------------------------------------- > > i.e. my normal user "jsmeix" has "rw" permissions. > > $ getfacl /dev/bus/usb/007/001 > getfacl: Removing leading '/' from absolute path names > # file: dev/bus/usb/007/001 > # owner: root > # group: users > user::rw- > group::r-- > other::r--
Now it is at least clear that the reason is something in the udev/HAL/resmgr machinery and - Thank God! - I am no expert here ;-) I assume you already tried a reboot with the scanner connected to the system? If I noticed correctly you can currently scan as normal user via running the saned (and the net backend) on your local host. Therefore there is currently no real loss of functionality. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
