Hello, On Jun 9 08:00 Bob Kline wrote (shortened): > I log into the machine as root, run > yast2, click on Hardware, then Scanners, and I see it run through an > unattended checklist ending with "Detecting USB and SCSI scanners" > after which it shows a line with "plustek Canon N1240U/LiDE30 at > plustek:libusb:007:002". If I click on Other ... Restart Detection > I end up with the same display. If I click Other ... Test I hear > the hardware make some noises and a bunch of tests are listed and > all marked as OK. If I then log into the machine as a normal user > and run xsane I end up with the "No devices available" message. Am > I missing a step in YAST?
No. It looks all well. Guess what: I have exactly such a Canon N1240U/LiDE30 here for testing and it always worked and works well for me, of course including "out-of-the-box" access as normal user. Therefore I cannot reproduce it and it is something very special why it doesn't work for you. All I can do is to provide some background information how the udev/HAL/resmgr machinery currently (for openSUSE 10.2) works: YaST sets scanner access permissions by calling /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which checks if the scanner is already listed in /etc/hal/fdi/policy/10osvendor/70-scanner.fdi and if not it writes /etc/hal/fdi/policy/10osvendor/80-scanner.fdi to set up HAL to trigger resmgr to grant access for normal users. For some background information have a look at https://bugzilla.novell.com/show_bug.cgi?id=218393 in particular start at comment #19. Don't get confused by "sane-dev", it was used for SCSI scanners. 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 --------------------------------------------------------------------- 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> --------------------------------------------------------------------- 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. 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 ---------------------------------------------------------------------- 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. 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]
