Re: Upgraded to woody and printing from KDE stopped
On Thu, 28 Mar 2002 21:54:04 -0700, Gruetzner wrote: > I did a search to see if others have had this problem, but didn't find >any. My apologies if I didn't use the right keywords. I've tried to use >the printing HOWTO, but seem to be going in circles when reading it. > > I recently upgraded from potato to woody. I did not upgrade the kernel >(2.2.19). My desktop is KDE. > >After upgrading, I could no longer get my printer to work. (It worked >under potato: I've a Brother HL-1240, and used the laserjet driver.) I >have since installed lprng and deleted lpr, and can now print an ascii >file from the command line (e.g., lpr testfile.txt). I > >However, when I try to print from a KDE app or from WordPerfect or >from acrobat, I get the following type of message window popping up: > > >/usr/bin/lpr -P 'lp|bhl1240|Brother HL-1240' '-#1' >/home/family/.kde/tmp-family/kdeprint_s5dkMry: execution failed with >message: > >Status Information: sending job '[EMAIL PROTECTED]' to >lp"bhl1240|Brother [EMAIL PROTECTED] connecting to 'localhost', attempt 1 >connected to 'localhost' requesting printer lp|bhl1240|Brother >[EMAIL PROTECTED] job 'family @localhost+433' transfer to >lp|bhl1240|Brother [EMAIL PROTECTED] failed error "NONZERO RFC1179 >ERROR CODE FROM SERVER' with ack 'ACK_FAIL' sending str >'^Blp|bhl1240|Brother-1240' to lp|[EMAIL PROTECTED] >error msg: 'bad command line' >--- > > I'm at a loss. I'm pretty ignorant of printing arcana, but something >must need configuring that isn't. > >Oh, I've tried it with the environmental variable $PRINTER set to "lp" >and to just nothing: same results. I've also tried... > # lpc enable all >...with no change. > > When I run lpq, it tells me that the last job that [EMAIL PROTECTED] > printed >was the lpr testfile.txt, and that Filter_status: lp is ready and >printing. (It's lying.) (What's this "@localhost bit?) Ready and printing means ready. @localhost is weird, have no clue. > > Running lsmod shows that lp is apparently loaded. I didn't see >anything that made sense to me in the /var/logs--but I may not know what >to look for! > >If you can help, I'd appreciate it, either on-list or direct. My >wife and eldest daughter are both bugging me to get the ability to print >back! James, I don't know that I'm offering much. I do think your printcap is screwy. The r=, p=, etc. are setup parameters and should not appear in the name of printer area. The apsfilter configurator will generate a printcap file for you. (Is apsfilter the latest?) Try renaming your existing printcap and run apsfilter config again. My Apsfilter-built printcap file is attached. "raw" is the printer name for my dot matrix using ASCII text and "pandot" is the name for the same printer when printing ps or other format. You must use the printer name in the print command (or it defaults to the unfiltered "lp") to get it to use the filter. Thus, lpr -Praw, or lpr -Ppandot. Before I learned this trick, my print jobs would, in some cases, disappear as do yours. (Don't know why it happens, I just avoid it.) Couple of notes, the bad printer name--all those parameters became part of the hl... name, and the 'can't find spool' error--each printer must have a file "/var/spool/lpd/" caveat: tested on gnome desktop using emacs and abiword -- gt Everything here could be wrong--Messiah's Handbook--Bach # /etc/printcap: printer capability database. See printcap(5). # You can use the filter entries df, tf, cf, gf etc. for # your own filters. See /etc/filter.ps, /etc/filter.pcl and # the printcap(5) manual page for further details. lp|Generic dot-matrix printer entry:\ :lp=/dev/lp0:\ :sd=/var/spool/lpd/lp:\ :af=/var/log/lp-acct:\ :lf=/var/log/lp-errs:\ :pl#66:\ :pw#80:\ :pc#150:\ :mx#0:\ :sh: # rlp|Remote printer entry:\ # :lp=:\ # :rm=remotehost:\ # :rp=remoteprinter:\ # :sd=/var/spool/lpd/remote:\ # :mx#0:\ # :sh: # APS1_BEGIN:printer1 # - don't delete start label for apsfilter printer1 # - no other printer defines between BEGIN and END LABEL pandot|Printer1 auto:\ :lp=/dev/lp0:\ :if=/etc/apsfilter/basedir/bin/apsfilter:\ :sd=/var/spool/lpd/pandot:\ :lf=/var/spool/lpd/pandot/log:\ :af=/var/spool/lpd/pandot/acct:\ :mx#0:\ :sh: raw|Printer1 raw:\ :lp=/dev/lp0:\ :if=/etc/apsfilter/basedir/bin/apsfilter:\ :sd=/var/spool/lpd/raw:\ :lf=/var/spool/lpd/raw/log:\ :af=/var/spool/lpd/raw/acct:\ :mx#0:\ :sf:\ :sh: # APS1_END - don't delete this
Re: Upgraded to woody and printing from KDE stopped
On Sat, Mar 30, 2002 at 09:51, Gruetzner wrote: >That is likely part of the problem. I need to research *how* to file a > bug report--and with whom? Apsfilter? Debian-kde? Someone else? Install package bug or better reportbug. Then you just type 'reportbug PACKAGENAME'. Make sure that your EMAIL variable is set correctly before that (with bash: 'export EMAIL="Your Name <[EMAIL PROTECTED]>' put this in your .bashrc) Finding the correct package name could be tricky sometimes. In your case, is there something like kprint? I do not know ... > > > A quick workaround is to login as root and to set in the KDE > > Control Center under System/printer the correct printer name. > > Then printing should work for you even with KDE. :-) Some of the things I have told you were wrong. I have checked all of it again and here is my solution: Reinstall apsfilter by calling apt-get --purge remove apsfilter apt-get install apsfilter apsfilterconfig lpc reread DO NOT edit the printcap file manually!!! Check if regular printing works with lpr PSFILE or a2ps ASCII-FILE. Ok, this should work now. Then in KDE (logged in as the regular user) go to ControlCenter->System->Printing and set the print system (at bottom) to UNIX-LPD-print-system. Now, printing for that user should work even from KDE. Test it by printing a text file from Konqueror. This worked for me and now my printing system is set up properly the first time. :-) Hope you can say the same afterwards. Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
On Friday 29 March 2002 23:36, Steffen Evers wrote: > On Fri, Mar 29, 2002 at 22:30, Gruetzner wrote: > > I then manually editted /etc/printcap, changing the semi-colon ( > > ; ) after hl1250 to a colon ( : ). That fixed one error message. > > The error message now reads: > > No, this was not good. > I have this line in my printcap file: > lp|cdj970;r=600x600;q=medium;c=full;p=a4;m=auto:\ > > Without knowing so much about the way apsfilter works, I guess > cdj970;r=600x600;q=medium;c=full;p=a4;m=auto > are parameters for apsfilter. So, you should not play around with these. > > Try printing a testpage with your old printcap (; instead of :). A catastrophe error message popped up: bad printer name. > Yes, you were right. This problem is not fixed in the current KDE > packages and you should file a bug. The parsing of the printer name > from the printcap file does not work properly. It should stop at the > first pipe '|' as pipes separate alternative names for the same > printer. However, it does not. That is likely part of the problem. I need to research *how* to file a bug report--and with whom? Apsfilter? Debian-kde? Someone else? > A quick workaround is to login as root and to set in the KDE > Control Center under System/printer the correct printer name. > Then printing should work for you even with KDE. :-) Well, I did that. It totally rewrote printcap to remove the filters, which was fine for simple text documents, but leaves a lot to be desired elsewhere! I went back and SETUP the apsfilter, and changed the first line from aps1|hl1250;r=600x600;q=medium;c=full;p=letter;m=auto:\ to aps1|hl1250:r=600x600;q=medium;c=full;p=letter;m=auto:\ This produced the "bad printer name" catastrophe. So, I changed it to aps1:r=600x600;q=medium;c=full;p=letter;m=auto:\ ...and it printed (from KWord)--except the first two lines were missing (outside the margins?) and there was only one typeface (~arial). However, fontsize (10pt, 12pt) and bolding appeared to work fine! Thanks again for the help. Eventually migrating to CUPS may help, but that appears to be a future try. Have a great day! James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
On Fri, Mar 29, 2002 at 22:30, Gruetzner wrote: > I then manually editted /etc/printcap, changing the semi-colon ( ; ) > after hl1250 to a colon ( : ). That fixed one error message. The error > message now reads: No, this was not good. I have this line in my printcap file: lp|cdj970;r=600x600;q=medium;c=full;p=a4;m=auto:\ Without knowing so much about the way apsfilter works, I guess cdj970;r=600x600;q=medium;c=full;p=a4;m=auto are parameters for apsfilter. So, you should not play around with these. Try printing a testpage with your old printcap (; instead of :). Yes, you were right. This problem is not fixed in the current KDE packages and you should file a bug. The parsing of the printer name from the printcap file does not work properly. It should stop at the first pipe '|' as pipes separate alternative names for the same printer. However, it does not. A quick workaround is to login as root and to set in the KDE Control Center under System/printer the correct printer name. Then printing should work for you even with KDE. :-) Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
I am trying to get printing services to work under woody. I've installed LPRng and apsfilter. An earlier error message indicated that (at least) the printcap file had an error. > > Based upon the kind advice of Steffen E., I installed apsfilter (and > > associated packages). The Test Page prints from apsfilterconfig just > > great. > Additionly, there seems to be somthiung wrong with the printername: > > hl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] > It should be 'hl1240' only! Are you sure, you are using current woody > packages? I remember having this problem earlier. If you are sure, your > problems are not fixed in current woody packages report about the > problem on debian-kde list. They will know more about KDE cups as well. Yes, I am using woody as of about an hour ago. I went and reran /usr/share/apsconfigure/SETUP, and am now using the hl1250 driver. The test page printed *beautifully*, but I still got an error message when printing. I then manually editted /etc/printcap, changing the semi-colon ( ; ) after hl1250 to a colon ( : ). That fixed one error message. The error message now reads: -- Status Information: sending job '[EMAIL PROTECTED]' to lp|[EMAIL PROTECTED] connecting to 'localhost',attempt 1 connected to 'localhost' requesting printer lp|[EMAIL PROTECTED] job 'family @localhost+680' transfer to lp|[EMAIL PROTECTED] failed error "NONZERO RFC1179 ERROR CODE FROM SERVER' with ack 'ACK_FAIL' sending str '^Blp|hl1250 to lp|[EMAIL PROTECTED] error msg: 'spool queue for 'lp_hl1250 does not exist on server localhost' error msg: 'non-existent printer or you need to run 'checkpc -f'' I ran checkpc -f; it gave no response. So...I think I'm making progress, but haven't gotten there yet! Do I need to do something special to set up a spool queue? > Anyway, your printer system should be set up correctly now. Try to print > something using lpr directly on a postscript file or a2ps. I did a $ lpr printtest.ps --and it printed all but the first line! (Albeit in the wrong font!) > Make sure you have set the papersize correctly in /etc/papersize and > /etc/a2ps.cfg (or something similar). Done: set for letter. Thanks again, Steffen. I appreciate the help you've given. Any other ideas? James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
On Fri, Mar 29, 2002 at 08:04, Gruetzner wrote: > Based upon the kind advice of Steffen E., I installed apsfilter (and > associated packages). The Test Page prints from apsfilterconfig just > great. Alas, I still can't print from within KDE, getting the error > message: > --- > /usr/bin/lpr -P > 'hl1240|laserjet';r=600x600;q=high;c=full;p=letter;m=auto '-#1' > /home/family/.kde/tmp-family/kdeprint_4h2doue: execution failed with > message: > > Status Information: sending job '[EMAIL PROTECTED]' to > hl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] > connecting to 'localhost',attempt 1 connected to 'localhost' requesting > printer hl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] > job 'family @localhost+579' transfer to > hl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] failed > error "NONZERO RFC1179 ERROR CODE FROM SERVER' with ack > 'ACK_FAIL' sending str > '^Bhl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] error > msg: 'bad printer name' > - > >I must admit that the printer name looks screwy, but that's what the > venerable apsfilter came up with. :-) > > I also wonder if there's something in KDE/woody. When installing, > dselect reported a conflict between kghostview and koffice-libs: > koffice-libs recommends kghostview (>= 2.2-0), but kghostview 2.1.1-6 is > what's in woody. > >Again, thanks to Steffan for his initial help. Alas, more is needed. The Linux print system is changing at the moment. There are three different systems as fare as I understand. 1. lpr: old BSD system 2. lprng: ng stands for next generation and is compatible to lpr, but should be more powerful 3. cups: I know little about it and I have never used it. KDE uses cups as fare as I do understand. The dependency problem with kghostview should be solved with current packages from a Debian ftp site. You should get a kghostview >= 2.2.2. When you do not find it in woody, get it from sid/unstable. Additionly, there seems to be somthiung wrong with the printername: > hl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] It should be 'hl1240' only! Are you sure, you are using current woody packages? I remember having this problem earlier. If you are sure, your problems are not fixed in current woody packages report about the problem on debian-kde list. They will know more about KDE cups as well. Anyway, your printer system should be set up correctly now. Try to print something using lpr directly on a postscript file or a2ps. Make sure you have set the papersize correctly in /etc/papersize and /etc/a2ps.cfg (or something similar). Godd luck. Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
On 29 Mar 2002, Gruetzner wrote: > I did a search to see if others have had this problem, but didn't find > any. My apologies if I didn't use the right keywords. I've tried to use > the printing HOWTO, but seem to be going in circles when reading it. > >I recently upgraded from potato to woody. I did not upgrade the kernel > (2.2.19). My desktop is KDE. > > After upgrading, I could no longer get my printer to work. (It worked > under potato: I've a Brother HL-1240, and used the laserjet driver.) I > have since installed lprng and deleted lpr, and can now print an ascii > file from the command line (e.g., lpr testfile.txt). I Can you print a postscript file from the command line? I would suggest throwing out lprng/lpr and trying CUPS instead. Try using the hl1250 driver (see http://www.linuxprinting.org/show_printer.cgi?recnum=234953 and http://www.linuxprinting.org/show_driver.cgi?driver=hl1250 ). Note that gs 6.53 is included in woody, so this should have the hl1250 as stated above. Note you can generate PPD files to interfact with the driver for use with cups using the links in the hl1250 page using ppdomatic or cupsomatic. Note you might need both of these; I'm not clear on that. See http://www.linuxprinting.org/ppd-doc.html and http://www.linuxprinting.org/cups-doc.html Disclaimer: I can't guarantee this will work. CUPS works flawlessly with Postscript printers, but with something like this it might be more flaky. Sincerely, Faheem Mitha. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
Based upon the kind advice of Steffen E., I installed apsfilter (and associated packages). The Test Page prints from apsfilterconfig just great. Alas, I still can't print from within KDE, getting the error message: --- /usr/bin/lpr -P 'hl1240|laserjet';r=600x600;q=high;c=full;p=letter;m=auto '-#1' /home/family/.kde/tmp-family/kdeprint_4h2doue: execution failed with message: Status Information: sending job '[EMAIL PROTECTED]' to hl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] connecting to 'localhost',attempt 1 connected to 'localhost' requesting printer hl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] job 'family @localhost+579' transfer to hl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] failed error "NONZERO RFC1179 ERROR CODE FROM SERVER' with ack 'ACK_FAIL' sending str '^Bhl1240|laserjet;r=600x600;q=high;c=full;p=letter;[EMAIL PROTECTED] error msg: 'bad printer name' - I must admit that the printer name looks screwy, but that's what the venerable apsfilter came up with. :-) I also wonder if there's something in KDE/woody. When installing, dselect reported a conflict between kghostview and koffice-libs: koffice-libs recommends kghostview (>= 2.2-0), but kghostview 2.1.1-6 is what's in woody. Again, thanks to Steffan for his initial help. Alas, more is needed. James On Friday 29 March 2002 04:34, Steffen Evers wrote: > On Thu, Mar 28, 2002 at 21:54, Gruetzner wrote: > > I did a search to see if others have had this problem, but didn't > > find any. My apologies if I didn't use the right keywords. I've > > tried to use the printing HOWTO, but seem to be going in circles when > > reading it. > > > >I recently upgraded from potato to woody. I did not upgrade the > > kernel (2.2.19). My desktop is KDE. > > > > After upgrading, I could no longer get my printer to work. (It > > worked under potato: I've a Brother HL-1240, and used the laserjet > > driver.) I have since installed lprng and deleted lpr, and can now > > print an ascii file from the command line (e.g., lpr testfile.txt). > > I > > > > However, when I try to print from a KDE app or from WordPerfect or > > from acrobat, I get the following type of message window popping up: > > > > > > /usr/bin/lpr -P 'lp|bhl1240|Brother HL-1240' '-#1' > > /home/family/.kde/tmp-family/kdeprint_s5dkMry: execution failed with > > message: > > > > Status Information: sending job '[EMAIL PROTECTED]' to > > lp"bhl1240|Brother [EMAIL PROTECTED] connecting to 'localhost', > > attempt 1 connected to 'localhost' requesting printer > > lp|bhl1240|Brother [EMAIL PROTECTED] job 'family @localhost+433' > > transfer to > > lp|bhl1240|Brother [EMAIL PROTECTED] failed error "NONZERO RFC1179 > > ERROR CODE FROM SERVER' with ack 'ACK_FAIL' sending str > > '^Blp|bhl1240|Brother-1240' to lp|[EMAIL PROTECTED] > > error msg: 'bad command line' > > --- > > > >I'm at a loss. I'm pretty ignorant of printing arcana, but > > something must need configuring that isn't. > > > > Oh, I've tried it with the environmental variable $PRINTER set to > > "lp" and to just nothing: same results. I've also tried... > ># lpc enable all > > ...with no change. > > > >When I run lpq, it tells me that the last job that [EMAIL PROTECTED] > > printed was the lpr testfile.txt, and that Filter_status: lp is ready > > and printing. (It's lying.) (What's this "@localhost bit?) > > > >Running lsmod shows that lp is apparently loaded. I didn't see > > anything that made sense to me in the /var/logs--but I may not know > > what to look for! > > I have been on woody for a while, but ran my regular package upgrade > lately which stopped my printing as well. > My printer has still received data, but could not print what it got. > > After spending several hours on debugging I have found out that my > current apsfilter settings (maybe you use the similar package > magicfilter) were not compatible with the current gs package > (ghostscript). After reconfigurating apsfilter with apsfilterconfig > everything has been fine again. However, it was a little bit > tricky to find a suitable printer driver that was supported in > apsfilter AND the current gs package as apsfilter has not been adjusted > to the recent changes in gs. > > Maybe that helps ... > > Good luck. > > Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgraded to woody and printing from KDE stopped
On Thu, Mar 28, 2002 at 21:54, Gruetzner wrote: > I did a search to see if others have had this problem, but didn't find > any. My apologies if I didn't use the right keywords. I've tried to use > the printing HOWTO, but seem to be going in circles when reading it. > >I recently upgraded from potato to woody. I did not upgrade the kernel > (2.2.19). My desktop is KDE. > > After upgrading, I could no longer get my printer to work. (It worked > under potato: I've a Brother HL-1240, and used the laserjet driver.) I > have since installed lprng and deleted lpr, and can now print an ascii > file from the command line (e.g., lpr testfile.txt). I > > However, when I try to print from a KDE app or from WordPerfect or > from acrobat, I get the following type of message window popping up: > > > /usr/bin/lpr -P 'lp|bhl1240|Brother HL-1240' '-#1' > /home/family/.kde/tmp-family/kdeprint_s5dkMry: execution failed with > message: > > Status Information: sending job '[EMAIL PROTECTED]' to > lp"bhl1240|Brother [EMAIL PROTECTED] connecting to 'localhost', attempt 1 > connected to 'localhost' requesting printer lp|bhl1240|Brother > [EMAIL PROTECTED] job 'family @localhost+433' transfer to > lp|bhl1240|Brother [EMAIL PROTECTED] failed error "NONZERO RFC1179 > ERROR CODE FROM SERVER' with ack 'ACK_FAIL' sending str > '^Blp|bhl1240|Brother-1240' to lp|[EMAIL PROTECTED] > error msg: 'bad command line' > --- > >I'm at a loss. I'm pretty ignorant of printing arcana, but something > must need configuring that isn't. > > Oh, I've tried it with the environmental variable $PRINTER set to "lp" > and to just nothing: same results. I've also tried... ># lpc enable all > ...with no change. > >When I run lpq, it tells me that the last job that [EMAIL PROTECTED] > printed > was the lpr testfile.txt, and that Filter_status: lp is ready and > printing. (It's lying.) (What's this "@localhost bit?) > >Running lsmod shows that lp is apparently loaded. I didn't see > anything that made sense to me in the /var/logs--but I may not know what > to look for! I have been on woody for a while, but ran my regular package upgrade lately which stopped my printing as well. My printer has still received data, but could not print what it got. After spending several hours on debugging I have found out that my current apsfilter settings (maybe you use the similar package magicfilter) were not compatible with the current gs package (ghostscript). After reconfigurating apsfilter with apsfilterconfig everything has been fine again. However, it was a little bit tricky to find a suitable printer driver that was supported in apsfilter AND the current gs package as apsfilter has not been adjusted to the recent changes in gs. Maybe that helps ... Good luck. Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
