Re: /dev/lp0 rights and CUPS

2006-07-05 Thread Olle Eriksson
On Monday 03 July 2006 19:31, Chris wrote:
 I have added lp to /etc/modules as was suggested in another message to
 this list.  Now I have  /dev/lp0 upon boot, but CUPS (localhost:631)
 complains:

 Unable to open parallel port device file /dev/lp0: Permission
 denied

 here are the versions I have installed.

 ii  cupsys 1.2.1-3Common UNIX Printing System(tm) -
 server ii  udev   0.093-1/dev/ and hotplug management
 daemon

 and here are the rights I am getting with this setup

 crw-rw 1 root lp 6, 0 2006-07-03 18:10 /dev/lp0

 why, oh why, can't udev and CUPS get along?   And how do I get udev to
 set the rights of /dev/lp0 to lp:lp which according to another posting
 is necessary to get let cupsd see it (it works if I manually do it)?

 I have the following in /etc/udev/permissions.d/udev.permissions

 printers/*:lp:lp:0660
 usb/lp[0-9]*:lp:lp:0660
 usb/legousbtower[0-9]*:root:root:666
 lp[0-9]*:lp:lp:0660
 parport[0-9]*:lp:lp:0660
 irlpt[0-9]*:root:lp:0660
 usblp[0-9]*:lp:lp:0660

 Any suggestions would be greatly (really!) appreciated,

I am no expert on udeb permission rules but that looks to me like you want 
the owner *and* group set to lp, with a permission of 660. But looking at 
the output of ls above you get root as the owner. Anyway that's what it 
looks like on my setup as well. I haven't had time to work with the udeb 
permissions (don't even have a udev.permissions on my etch setup), but I 
only got it to work when I set the permissions to 666. I do that from a 
startup script now. Not very nice I know but it works. Let me know if it 
helps.

Best regards


-- 
Olle Eriksson | Software Engineer
[EMAIL PROTECTED] | http://www.olle-eriksson.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Re: /dev/lp0 rights and CUPS

2006-07-05 Thread Christof Hurschler

 Original-Nachricht 
Datum: Wed, 5 Jul 2006 08:25:58 +0200
Von: Olle Eriksson [EMAIL PROTECTED]
An: 
Betreff: Re: /dev/lp0 rights and CUPS

 On Monday 03 July 2006 19:31, Chris wrote:
  I have added lp to /etc/modules as was suggested in another message to
  this list.  Now I have  /dev/lp0 upon boot, but CUPS (localhost:631)
  complains:
 
  Unable to open parallel port device file /dev/lp0: Permission
  denied
 
  here are the versions I have installed.
 
  ii  cupsys 1.2.1-3Common UNIX Printing System(tm) -
  server ii  udev   0.093-1/dev/ and hotplug management
  daemon
 
  and here are the rights I am getting with this setup
 
  crw-rw 1 root lp 6, 0 2006-07-03 18:10 /dev/lp0
 
  why, oh why, can't udev and CUPS get along?   And how do I get udev to
  set the rights of /dev/lp0 to lp:lp which according to another posting
  is necessary to get let cupsd see it (it works if I manually do it)?
 
  I have the following in /etc/udev/permissions.d/udev.permissions
 
  printers/*:lp:lp:0660
  usb/lp[0-9]*:lp:lp:0660
  usb/legousbtower[0-9]*:root:root:666
  lp[0-9]*:lp:lp:0660
  parport[0-9]*:lp:lp:0660
  irlpt[0-9]*:root:lp:0660
  usblp[0-9]*:lp:lp:0660
 
  Any suggestions would be greatly (really!) appreciated,
 
 I am no expert on udeb permission rules but that looks to me like you want
 the owner *and* group set to lp, with a permission of 660. But looking at 
 the output of ls above you get root as the owner. Anyway that's what it 
 looks like on my setup as well. I haven't had time to work with the udeb 
 permissions (don't even have a udev.permissions on my etch setup), but I 
 only got it to work when I set the permissions to 666. I do that from a 
 startup script now. Not very nice I know but it works. Let me know if it 
 helps.
 

I guess I wasn't clear in my previous post, the changes I made to 
udev.permissions did *not* change the owner from root to lp on the next boot.

I did change the printers in the rules file (as suggested for the usb entry 
in previous post in this thread) and that seems to have worked.

Can some of the more experienced Debian users on this list explain what is 
going on here?  It seems obvious to me that cupsd should be run with rights 
that allow it to access printers, shouldn`t it?

Thanks,

Chris 
-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: /dev/lp0 rights and CUPS

2006-07-05 Thread John O'Hagan
On Wednesday 05 July 2006 02:25, Chris wrote:

 I don't have a usb printer so the line you used in local.rules does'nt work 
for me.

Just replace usb in the rule with whatever bus your printer appears on, and 
hopefully that will fix your permission issue.

See /usr/share/doc/udev/writing_udev_rules/index.html (this should be on your 
system), also man udevinfo.

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Re: /dev/lp0 rights and CUPS

2006-07-04 Thread Christof Hurschler
 On Tuesday 04 July 2006 03:31, Chris wrote:
  I have added lp to /etc/modules as was suggested in another message to
 this
  list.  Now I have  /dev/lp0 upon boot, but CUPS (localhost:631)
 complains:
 
  Unable to open parallel port device file /dev/lp0: Permission denied
 
  here are the versions I have installed.
 
  ii  cupsys 1.2.1-3Common UNIX Printing System(tm) -
 server
  ii  udev   0.093-1/dev/ and hotplug management daemon
 
  and here are the rights I am getting with this setup
 
  crw-rw 1 root lp 6, 0 2006-07-03 18:10 /dev/lp0
 
  why, oh why, can't udev and CUPS get along?   And how do I get udev to
 set
  the rights of /dev/lp0 to lp:lp which according to another posting is
  necessary to get let cupsd see it (it works if I manually do it)?
 
 
 
 In /etc/udev/local.rules, I have the line:
 
 BUS==usb, KERNEL==lp[0-9]*, OWNER=lp
 
 which makes sure the ownership of /dev/usb/lp0 is right for my usb
 printer. 
 (The group is automatically taken care of in permissions.rules - but 
 strangely not the owner.)
 
 I find I also have to use an old /etc/cups/cupsd.conf file if I want to
 print 
 as a user (from KDE at least) - I'm in the process of trying to work out
 why.


Judging by the limited response to my post this doesn't seem to be a widespread 
problem.  Although I'm a real Debian fan, it took me a while to get to the 
bottom of this problem and I must say I'm really frustrated.  This seems like a 
basic issue:  cupsd should run with rights that allow it to access printers - 
or am I missing something here?

Thanks for your post, I'll try what you suggested!

Chris
-- 


Feel free – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: /dev/lp0 rights and CUPS

2006-07-04 Thread Chris
On Tuesday 04 July 2006 06:41, John O'Hagan wrote:
 On Tuesday 04 July 2006 14:27, John O'Hagan wrote:
  I find I also have to use an old /etc/cups/cupsd.conf file if I want to
  print as a user (from KDE at least) - I'm in the process of trying to
  work out why.

 It was because the new /etc/cups/cupsd.conf contains:

   # Only listen for connections from the local machine.
   Listen localhost:631
   Listen /var/run/cups/cups.sock

 The third line was causing permission problems for normal users; commenting
 it out fixed it.

 John

I did that and restarted cupsd, it didn't help.  I don't have a usb printer so 
the line you used in local.rules does'nt work for me.

Chris
-- 
C. Hurschler


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: /dev/lp0 rights and CUPS

2006-07-04 Thread Ken Wahl
On Tue, Jul 04, 2006 at 02:41:59PM +1000, John O'Hagan wrote:
 It was because the new /etc/cups/cupsd.conf contains:
 
   # Only listen for connections from the local machine.
   Listen localhost:631
   Listen /var/run/cups/cups.sock
 

Thanks, John. Commenting out line 3 fixed the kdeprint/cups1.2
incompatibility problem (1,2,3) on Sid for me.

(1) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=370403
(2) http://bugs.kde.org/show_bug.cgi?id=115891
(3) http://www.kdedevelopers.org/node/1901

-- 
Ken Wahl


signature.asc
Description: Digital signature


Re: /dev/lp0 rights and CUPS

2006-07-03 Thread John O'Hagan
On Tuesday 04 July 2006 03:31, Chris wrote:
 I have added lp to /etc/modules as was suggested in another message to this
 list.  Now I have  /dev/lp0 upon boot, but CUPS (localhost:631) complains:

 Unable to open parallel port device file /dev/lp0: Permission denied

 here are the versions I have installed.

 ii  cupsys 1.2.1-3Common UNIX Printing System(tm) - server
 ii  udev   0.093-1/dev/ and hotplug management daemon

 and here are the rights I am getting with this setup

 crw-rw 1 root lp 6, 0 2006-07-03 18:10 /dev/lp0

 why, oh why, can't udev and CUPS get along?   And how do I get udev to set
 the rights of /dev/lp0 to lp:lp which according to another posting is
 necessary to get let cupsd see it (it works if I manually do it)?



In /etc/udev/local.rules, I have the line:

BUS==usb, KERNEL==lp[0-9]*, OWNER=lp

which makes sure the ownership of /dev/usb/lp0 is right for my usb printer. 
(The group is automatically taken care of in permissions.rules - but 
strangely not the owner.)

I find I also have to use an old /etc/cups/cupsd.conf file if I want to print 
as a user (from KDE at least) - I'm in the process of trying to work out why.

HTH,

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: /dev/lp0 rights and CUPS

2006-07-03 Thread John O'Hagan
On Tuesday 04 July 2006 14:27, John O'Hagan wrote:


 I find I also have to use an old /etc/cups/cupsd.conf file if I want to
 print as a user (from KDE at least) - I'm in the process of trying to work
 out why.


It was because the new /etc/cups/cupsd.conf contains:

# Only listen for connections from the local machine.
Listen localhost:631
Listen /var/run/cups/cups.sock

The third line was causing permission problems for normal users; commenting it 
out fixed it.

John


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]