Re: Does apsfilter work?
I had *lots* of problems with this, what eventually worked best for me was to install lprng package and go the lprng webpage. There it gives instructions and commands to set the proper permissions. After that, everything works well. HTH [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi Nelson, do you mean that now your apsfilter is up and running ( in other words is yours a suggestion to fix the problem) or did you abandon apsfilter? Vittorio -- Forwarded Message -- Subject: Re: Problems with printing Date: Wed, 2 May 2001 09:56:29 -0400 From: Wayne Topa [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Re: Problems with printing Date: Wed, May 02, 2001 at 06:59:34AM - In reply to:[EMAIL PROTECTED] Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): Well, Wayne, I don't really think a Debian potato distribution fails in a strategic and basic piece of software such as apsfilter. I rather think there's something wrong in my configuration relating to authorizations but I don't know where and what to manipulate. Perhaps I missed to define some special group, or whatever else. What strikes me is that the test which apsfilterconfig suggests works great, while any following attempt to print dies unexpectedly. Any suggestion to fix it before eliminating apsfilter? Vittorio I just set up apsfilter last night, and I had the same problem--the test page printed fine, and I could cat stuff directly, but everything else failed. It turns out that the permissions of the printer device in /dev were set wrong-- read-only, no write for the lp group, which obviously doesn't make much sense for a printer using lprng for spooling. -Nelson - messaggio inviato con Freemail by superEva http://www.supereva.it - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Does apsfilter work?
Hi Nelson, do you mean that now your apsfilter is up and running ( in other words is yours a suggestion to fix the problem) or did you abandon apsfilter? Vittorio -- Forwarded Message -- Subject: Re: Problems with printing Date: Wed, 2 May 2001 09:56:29 -0400 From: Wayne Topa [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Re: Problems with printing Date: Wed, May 02, 2001 at 06:59:34AM - In reply to:[EMAIL PROTECTED] Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): Well, Wayne, I don't really think a Debian potato distribution fails in a strategic and basic piece of software such as apsfilter. I rather think there's something wrong in my configuration relating to authorizations but I don't know where and what to manipulate. Perhaps I missed to define some special group, or whatever else. What strikes me is that the test which apsfilterconfig suggests works great, while any following attempt to print dies unexpectedly. Any suggestion to fix it before eliminating apsfilter? Vittorio I just set up apsfilter last night, and I had the same problem--the test page printed fine, and I could cat stuff directly, but everything else failed. It turns out that the permissions of the printer device in /dev were set wrong-- read-only, no write for the lp group, which obviously doesn't make much sense for a printer using lprng for spooling. -Nelson - messaggio inviato con Freemail by superEva http://www.supereva.it -
Does apsfilter work?
-- Forwarded Message -- Subject: Re: Problems with printing Date: Wed, 2 May 2001 09:56:29 -0400 From: Wayne Topa [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Re: Problems with printing Date: Wed, May 02, 2001 at 06:59:34AM - In reply to:[EMAIL PROTECTED] Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): Well, Wayne, I don't really think a Debian potato distribution fails in a strategic and basic piece of software such as apsfilter. I rather think there's something wrong in my configuration relating to authorizations but I don't know where and what to manipulate. Perhaps I missed to define some special group, or whatever else. What strikes me is that the test which apsfilterconfig suggests works great, while any following attempt to print dies unexpectedly. Any suggestion to fix it before eliminating apsfilter? Vittorio Well I messed with it for a few hours and could never get it to print anything as nice as the test page (which was really nice). I read all the docs but could not get the results I wanted on the printer. I am sure that it is a good package as many people do use it. I just could not get it working correctly. That said, maybe someone else can point you to what need fixing. Magicfilter took less then 5 minutes to get working and another few minutes to set up a2ps and i was up and runing. I needed a working printer so I took the path of least resistance. BTW, you should set your lines to a 70-72 char length for this list. Good luck! You should be getting responses from those who did get apsfilter running. regards -- Everyone can be taught to sculpt: Michelangelo would have had to be taught how __not to. So it is with the great programmers. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ---
Re: Does apsfilter work?
-- Forwarded Message -- Subject: Re: Problems with printing Date: Wed, 2 May 2001 09:56:29 -0400 From: Wayne Topa [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Re: Problems with printing Date: Wed, May 02, 2001 at 06:59:34AM - In reply to:[EMAIL PROTECTED] Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): Well, Wayne, I don't really think a Debian potato distribution fails in a strategic and basic piece of software such as apsfilter. I rather think there's something wrong in my configuration relating to authorizations but I don't know where and what to manipulate. Perhaps I missed to define some special group, or whatever else. What strikes me is that the test which apsfilterconfig suggests works great, while any following attempt to print dies unexpectedly. Any suggestion to fix it before eliminating apsfilter? Vittorio I just set up apsfilter last night, and I had the same problem--the test page printed fine, and I could cat stuff directly, but everything else failed. It turns out that the permissions of the printer device in /dev were set wrong-- read-only, no write for the lp group, which obviously doesn't make much sense for a printer using lprng for spooling. -Nelson
