Hello, On Oct 11 09:50 Kenneth Schneider wrote (shortened):
Mine are: crw-rw-r-- 1 root lp 189, 3 2007-10-10 20:00 /dev/bus/usb/001/004
When you set up the scanner unit with YaST, it runs /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which does some magic to determine the USB device ID and write it to /etc/hal/fdi/policy/10osvendor/80-scanner.fdi so that the udev/HAL/resmgr machinery could do its magic to set an appropriate ACL for the /dev/bus/usb/xxx/yyy device file. But the udev/HAL machinery doesn't notice changed *.fdi files in the running system, see https://bugzilla.novell.com/show_bug.cgi?id=218393#c28 so that only a restart of HAL helps (or a reboot). Or the magic in test_and_set_scanner_access_permissions may not work for your particular model so that there is no entry in 80-scanner.fdi. In this case see http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.070704... for several ways how to do it manually - perhaps you like it more to add the users who should be allowed to scan to the "lp" group.
The simplest solution is to use the saned and the net meta-backend on your local host to access the scanner, for example via "YaST scanner setup" -> "Other" -> "Scanning via Network".
This did the trick, thank you very much.
But the little drawback is that now scanning-frontends for root will "see" the scanner twice. Once directly as "hpaio:..." and a duplicate via the net meta-backend as "net:localhost:hpaio:..." (compare the "scanimage -L" output as root and as normal user). Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org