On Thu, May 07, 2009 at 05:03:21PM +0100, lux-integ wrote: > On Thursday 07 May 2009 02:36:06 pm Ken Moffat wrote: > > > I'm assuming you (as a user) are in the group 'lp' and that you > > have perms like > > this: > > > > k...@bluesbreaker ~ $ls -l /dev/usb > > total 0 > > crw-rw---- 1 root lp 180, 0 2009-05-07 14:25 lp0 > > I have > crw-rw--r-- 1 root lp 180, 0 2009-05-07 xx.yy lp0 > it is the same reported by a suse11 on the machine. > > ( I have never tried to use chmod on a special file (i.e. with c). So > if > the c664 reporting for //dev/usb is inadequate I would be grateful if you > (or anyone one on list could comment and on how this might be modified.) > > cheers > lux-integ >
First, my perms are slightly tighter than yours (user=owner, group, other) although letting anyone read it might be useful if people who check the ink levels are different from whoever ends up doing the printing (group lp, I assume). So, no immediate reason to change them and certainly not an obvious solution to your problem. Second, all device special files are transient under udev - they get recreated across boots. You can chmod them to see if it helps, but for long-term fixes you would need to alter the rule. For debugging, particularly for problems with sound or lack of, chmod is a useful tool to see if a change helps, just chmod the device like any other file - and the same for chown. Since you haven't commented on my assumption, I'll be rude and ask directly - is the user doing the printing a member of the lp group ? If the answer to that is yes, I think you'll have to alter cupsd.conf like I said earlier (edit, bounce cups [ 'restart' is I think the preferred term here, although I always think that sounds as if it is already stopped ]), try to print one item (test page or whatever - the web interface is easiest for this), then spend time looking at the log to see what fails. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
