On 09/14/2007 03:12 PM, Johannes Meixner wrote: > On Sep 14 08:06 Joe Morris (NTM) wrote (shortened): > >> On 09/13/2007 10:34 PM, Johannes Meixner wrote: >> >>> it seems there is by default no device status via hp-toolbox >>> for normal users which do not have write access to a USB printer >>> even if hpssd runs as root. >>> >>> >> It works here in 10.2 >> > > It works only for all-in-one devices where a scanner is included > and when the scanner unit was set up with YaST. > It does not work out-of-the box for a plain printer. > In the past I fooled myself by testing it with my HP LaserJet 1220 > which has a scanner unit. > I see. I did not understand the difference for a plain printer and an AIO. I guess I had not even thought about a regular printer with hplip, but of course that is the only way to be able to keep track of the details regarding a regular hp printer, such as ink levels. Does it work if the users are members of the lp group? >> [EMAIL PROTECTED]:~> ls -l /dev/bus/usb/004/002 >> crw-rw-r--+ 1 root lp 189, 385 2007-09-14 06:27 /dev/bus/usb/004/002 >> > > Note the '+' which indicates the ACL set via HAL/resmgr because > of the scanner unit which grants access for the user who is > locally logged in (i.e. via "console"/XDM/KDM). > Such an ACL is not set for a plain printer. > I see. I learn so much from you. ;-) > >>> [EMAIL PROTECTED] lpstat -v >>> device for deskjet_3320: hp:/usb/deskjet_3320?serial=TH27T2H35B35 >>> >>> >> [EMAIL PROTECTED]:~> lpstat -v >> device for HP_PSC2175: hp:/usb/PSC_2170_Series?serial=MY3AEF74PF73 >> > > Here you see the difference: > My DeskJet 3320 is a plain printer, your PSC 2175 has a scanner > included and I assume you did set up the scanner unit with YaST > which creates a matching HAL/resmgr entry in > /etc/hal/fdi/policy/10osvendor/80-scanner.fdi > I did try with Yast, and through some help from one of your posts here I got the entry corrected for my kernel and yes it has been working ever since. > > > If I had a list of USB product IDs for HP printers, I could create > a matching /etc/hal/fdi/policy/10osvendor/80-HPprinter.fdi file > to grant read/wrire access even for HP printers for locally logged > in users. > > If I had a list of USB product IDs for all HPLIP supported devices, > I could create a matching /etc/hal/fdi/policy/10osvendor/70-hplip.fdi > file to grant the access out-of-the box for HPLIP devices even without > the need to do the permission stuff via YaST for HP all-in-one devices. > > If there was a list of USB product IDs for all HPLIP supported devices, > even the udev rules would be correct and would no longer set HPLIP > permissions for any HP USB device. In particular no longer read access > for all users for a HP USB mass storage device or a HP USB keyboard. > (If any user can read the keyboard, any user may be able to read the > keystrokes e.g. when the login password is typed.) > That all sounds like some really great ideas. Is this something users could help with, or would HP be willing to supply the product IDs? I think this could be a tremendous advantage to HP printers sales in the Linux market, the easier it is to get them working (which hplip has made great strides) and working well. I truly hope your ideas become a reality!
-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ HPLIP-Help mailing list HPLIP-Help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hplip-help
