Re: /dev/lp0 - Permission denied after CUPS upgrade

2007-02-23 Thread Luigi D. C.
Hi, Mr. Marcelo I had your same trouble periodically resurfacing with cups upgrades on my debian! I solved it now changing group name (to "lp" instead of "root") on all cups related files in usr/bin and usr/sbin chown root.lp I hope this can help David -- Luigi D. C. <[EMAIL PROTECTED]> -- To U

Re: /dev/lp0 - Permission denied after CUPS upgrade

2006-10-29 Thread Chris
On Sunday 29 October 2006 20:30, Colin wrote: > Chris wrote: > > This is an older post from a while back. The problem seems to have > > resurfaced. On my machine after a reboot, I have: > > > > crw-rw 1 root lp 6, 0 2006-10-29 20:03 /dev/lp0 > > > > I can't use the printer until I change it t

Re: /dev/lp0 - Permission denied after CUPS upgrade

2006-10-29 Thread Colin
Chris wrote: This is an older post from a while back. The problem seems to have resurfaced. On my machine after a reboot, I have: crw-rw 1 root lp 6, 0 2006-10-29 20:03 /dev/lp0 I can't use the printer until I change it to lp:lp or chmod 777. I'm guessing this is a udev problem, but how

Re: /dev/lp0 - Permission denied after CUPS upgrade

2006-10-29 Thread Chris
This is an older post from a while back. The problem seems to have resurfaced. On my machine after a reboot, I have: crw-rw 1 root lp 6, 0 2006-10-29 20:03 /dev/lp0 I can't use the printer until I change it to lp:lp or chmod 777. I'm guessing this is a udev problem, but how do I fix it fo

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

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 >

Re: /dev/lp0 rights and CUPS

2006-07-04 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 ver

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 th

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

Re: Re: /dev/lp0 rights and CUPS

2006-07-03 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" > > > > h

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

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 versio

Re: client-error-not-found [was: Re: /dev/lp0 - Permission denied after CUPS upgrade]

2006-06-26 Thread Wayne Topa
Marcelo Luiz de Laia([EMAIL PROTECTED]) is reported to have said: > > I did this: purge and reinstal, and, now, I get another error: > > client-error-not-found > > on GtkLPq status bar. > > When I access the printer by web (localhost:631) I can see it and it was > started! But it dosent print

client-error-not-found [was: Re: /dev/lp0 - Permission denied after CUPS upgrade]

2006-06-26 Thread Marcelo Luiz de Laia
Wayne Topa wrote: I had the same problem. I purged all of the cups packages and reinstalled them and that fixed it. I believe it had to do with some of the old 1.1 cups files not being deleted when I did the cups 1.32 upgrade. Hope this helps Wayne I did this: purge and reinstal, and, n

Re: /dev/lp0 - Permission denied after CUPS upgrade

2006-06-23 Thread Mike McCarty
Marcelo Luiz de Laia wrote: After upgrade I am not able to print with my user. Please, see the out put commands: ~$ ls -la /dev/lp0 crw-rw 1 root lp 6, 0 2006-06-13 07:16 /dev/lp0 This looks correct to me. If I chang de /dev/lp0 owner by: ~$ sudo chown lp /dev/lp0 ~$ ls -la /dev/lp0

Re: /dev/lp0

2003-09-02 Thread Russell Shaw
Elie De Brauwer wrote: On Tuesday 02 September 2003 11:51, Russell Shaw wrote: Elie De Brauwer wrote: On Tuesday 02 September 2003 11:39, Russell Shaw wrote: Hi, When i do: cp test.txt /dev/lp0 shouldn't it blindly copy the text to the port and return immediately? (it hangs) That depends, in som

Re: /dev/lp0

2003-09-02 Thread Elie De Brauwer
On Tuesday 02 September 2003 11:51, Russell Shaw wrote: > Elie De Brauwer wrote: > > On Tuesday 02 September 2003 11:39, Russell Shaw wrote: > >>Hi, > >>When i do: cp test.txt /dev/lp0 > >>shouldn't it blindly copy the text > >>to the port and return immediately? > >>(it hangs) > > > > That depends

Re: /dev/lp0

2003-09-02 Thread Russell Shaw
Pim Bliek | PingWings.nl wrote: I'm not sure if this will do what you expect (I'm not behind a Debian box now so I cannot check) but why don't u try: cat file.txt > /dev/lp0 ?? That hangs the same way too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Con

Re: /dev/lp0

2003-09-02 Thread Russell Shaw
Elie De Brauwer wrote: On Tuesday 02 September 2003 11:39, Russell Shaw wrote: Hi, When i do: cp test.txt /dev/lp0 shouldn't it blindly copy the text to the port and return immediately? (it hangs) That depends, in some cases that could work unless you have a printer like hp deskjet 710, 720 etc w

Re: /dev/lp0

2003-09-02 Thread Pim Bliek | PingWings.nl
I'm not sure if this will do what you expect (I'm not behind a Debian box now so I cannot check) but why don't u try: cat file.txt > /dev/lp0 ?? Good luck! Pim - PingWings - the penguin provides profit - - - - - - - - - - - - - - - - - - - - - - - M:

Re: /dev/lp0

2003-09-02 Thread Elie De Brauwer
On Tuesday 02 September 2003 11:39, Russell Shaw wrote: > Hi, > When i do: cp test.txt /dev/lp0 > shouldn't it blindly copy the text > to the port and return immediately? > (it hangs) That depends, in some cases that could work unless you have a printer like hp deskjet 710, 720 etc who require add

Re: /dev/lp0

2003-09-02 Thread Tom Badran
On Tuesday 02 Sep 2003 10:39, Russell Shaw wrote: > Hi, > When i do: cp test.txt /dev/lp0 > shouldn't it blindly copy the text > to the port and return immediately? > (it hangs) Its a character device so it will block while it is processing each charcter. If there is no device responding it will

Re: /dev/lp0: No such device

2001-07-11 Thread Joost Kooij
On Tue, Jul 10, 2001 at 06:51:47PM -0500, Dave Sherohman wrote: > I've built myself a 2.4.5 kernel with parport support, but it appears > to be broken, as any attempt to print (whether to /dev/lp0, lp1, lp2, > par0, par1, or par2) results in the error "No such device". > /var/log/syslog records the

Re: /dev/lp0: No such device

2001-07-11 Thread Dave Sherohman
On Tue, Jul 10, 2001 at 11:19:25PM -0400, Wayne Topa wrote: > # Character devices > # > CONFIG_PRINTER=y That was it. Thanks. Am I the only one who considers it a bug that "Parallel printer support" (and, for that matter, "Support for user-space parallel port device drivers") is under "Character

Re: /dev/lp0: No such device

2001-07-10 Thread Wayne Topa
Subject: /dev/lp0: No such device Date: Tue, Jul 10, 2001 at 06:51:47PM -0500 In reply to:Dave Sherohman Quoting Dave Sherohman([EMAIL PROTECTED]): > I've built myself a 2.4.5 kernel with parport support, but it appears > to be broken, as any attempt to print (whether to /dev/lp0

Re: /dev/lp0 does not exist

2000-04-24 Thread Oswald Buddenhagen
> Attachment 1: > debian_arc:~# insmod sg > Using /lib/modules/2.2.14/scsi/sg.o > /lib/modules/2.2.14/scsi/sg.o: unresolved symbol scsi_init_free_R6ac8ba0b > ... i'm definitely not sure about this, but it may have something to do with the "Set version information on all symbols for modules" kernel

Re: /dev/lp0 does not exist

2000-04-24 Thread Antonio Rodriguez
Well, the problem is then more serious, related to something that I posted a while ago, but got no response. I will appreciate any help. Next the attachment: Attachment 1: debian_arc:~# insmod sg Using /lib/modules/2.2.14/scsi/sg.o /lib/modules/2.2.14/scsi/sg.o: unresolved symbol scsi_init_free_R6

Re: /dev/lp0 does not exist

2000-04-24 Thread Oswald Buddenhagen
> When I try echo "hello" > /dev/lp0 (or lp1,2,3) I get something like > device doesn't exist. But it is there? Where is the problem? Any ideas? > the special file is always there - it's installed with linux itself. you must compile printer support in the kernel or load the right modules. all ker

Re: /dev/lp0 quit after kernel "modulized"...

1999-10-12 Thread Phil Brutsche
A long time ago, in a galaxy far, far way, someone said... > Mirek: > > > Hmm, it not a problem. Add alias: > > > >alias parport_lowlevel parport_pc > > > > and all is fine: > > > I tried that (by adding that line to /etc/modutils/aliases - correct > way?)... That's part of the correct w

Re: /dev/lp0 quit after kernel "modulized"...

1999-10-12 Thread rich
Mirek: > Hmm, it not a problem. Add alias: > >alias parport_lowlevel parport_pc > > and all is fine: I tried that (by adding that line to /etc/modutils/aliases - correct way?)... didn't change anything... Can the parallel port be used as a module for printing? > monkeyhouse:/home/rich#

Re: /dev/lp0 quit after kernel "modulized"...

1999-10-11 Thread Mirek Kwasniak
On Mon, Oct 11, 1999 at 08:39:23AM +0200, Jean-Yves BARBIER wrote: > On Sun, Oct 10, 1999 at 10:16:37PM -0500, rich wrote: > > Howdy all, > > . > > monkeyhouse:/home/rich# cat temp.txt > /dev/lp0 > > bash: /dev/lp0: Operation not supported by device > > > > However, the output of 'lsmod' shows

Re: /dev/lp0 quit after kernel "modulized"...

1999-10-11 Thread Jean-Yves BARBIER
On Sun, Oct 10, 1999 at 10:16:37PM -0500, rich wrote: > Howdy all, > . > monkeyhouse:/home/rich# cat temp.txt > /dev/lp0 > bash: /dev/lp0: Operation not supported by device > > However, the output of 'lsmod' shows that lp and parport are loaded > any ideas? > > Module Siz