On Wednesday 08 April 2009 03:02:29 Anders Boström wrote: > eckert:~# ll /dev/bus/usb/007/003 > crw-rw-r-- 1 root lp 189, 770 Apr 7 18:49 /dev/bus/usb/007/003 > eckert:~# > > And I understand your lp group question now. > > But this is most unlogical, that you have to be a member of the lp > group in order to scan, but not in order to print. And that being a > member of the scanner group isn't sufficient in order to scan. Yes I know it seems a bit crazy. But I would anticipate that while you can print, you can't access the functions from the hp systray - ink levels, jobs etc. For a while we did try to setup that you had to be a member of the lp group for printing functions and scanner group for printing+scanning functions, but there was too much overlap, like ink levels. So with 3.9.2 we have tried to standardise on the lp group for everything. But that is still causing confusion. We also dabbled with the plugdev group for access to plugged in devices, but that was causing confusion too. What I would to be able to do is have the console user have full functional access to plugged in multi-function devices. But I haven't been able to work the udev rules to accomplish. Mark Ideally I would like to have the console user by default gets access.
Attachment:
signature.asc
Description: This is a digitally signed message part.