From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 Description of problem: Foomatic / lpr will not print an ascii file to the printer either through the command line or through the printconf TUI tool. I get the following message in /var/spool/lpd/<printername>/lpq.0: Status: IF filter 'mf_wrapper' filter msg - '/usr/share/printconf/util/printconf_mfomatic.pl: running: gs -q -dBATCH -dSAFER -dQUIET -dNOPAUSE -sDEVICE=bjc600 -sOutputFile=- -' at 00:16:14.646 Status: IF filter 'mf_wrapper' filter msg - '/usr/share/printconf/util/printconf_mfomatic.pl: ascii job. wtf! we don't do ascii in mfomatic' at 00:16:14.646 Status: IF filter 'mf_wrapper' filter msg - 'we don't do ascii in mfomatic! at /usr/share/printconf/util/printconf_mfomatic.pl line 407.' at 00:16:14.646 Status: IF filter 'mf_wrapper' filter exit status 'UNKNOWN STATUS '255'' at 00:16:14.654 Status: printing finished at 00:16:14.655 Status: accounting at end at 00:16:14.655 Status: finished 'poo@anakin+829', status 'UNKNOWN STATUS '255'' at 00:16:14.655 Status: subserver pid 23831 exit status 'UNKNOWN STATUS '255'' at 00:16:14.656 Status: job 'cfA829anakin.loki.net' error 'aborting operations' at 00:16:14.656 Status: removing job 'cfA829anakin.loki.net' - ABORT at 00:16:14.657 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Run 'setup' and select the printconf tool, setup Cannon BJC 3000 with the bjc6000 driver set. 2. Create a text file, only ascii text, named foo.txt 3. lpr foo.txt, job gets aborted. Actual Results: Status: IF filter 'mf_wrapper' filter msg - '/usr/share/printconf/util/printconf_mfomatic.pl: running: gs -q -dBATCH -dSAFER -dQUIET -dNOPAUSE -sDEVICE=bjc600 -sOutputFile=- -' at 00:16:14.646 Status: IF filter 'mf_wrapper' filter msg - '/usr/share/printconf/util/printconf_mfomatic.pl: ascii job. wtf! we don't do ascii in mfomatic' at 00:16:14.646 Status: IF filter 'mf_wrapper' filter msg - 'we don't do ascii in mfomatic! at /usr/share/printconf/util/printconf_mfomatic.pl line 407.' at 00:16:14.646 Status: IF filter 'mf_wrapper' filter exit status 'UNKNOWN STATUS '255'' at 00:16:14.654 Status: printing finished at 00:16:14.655 Status: accounting at end at 00:16:14.655 Status: finished 'poo@anakin+829', status 'UNKNOWN STATUS '255'' at 00:16:14.655 Status: subserver pid 23831 exit status 'UNKNOWN STATUS '255'' at 00:16:14.656 Status: job 'cfA829anakin.loki.net' error 'aborting operations' at 00:16:14.656 Status: removing job 'cfA829anakin.loki.net' - ABORT at 00:16:14.657 Expected Results: A successful printing of an ascii text file. Additional info: I get the same message when trying to test print an ascii page from the printconf TUI. The postscript test page prints just fine, and since the printer is shared out through samba, remote win32 clients can print all day long without issues.
I don't think you have applied all the updates. Does this problem still occur after you have applied the updates (you can use up2date for that)?
Yes, I am fully updated, aside from the 'print-conf' package. When I update the print-conf package, and try to configure a printer, nothing ever gets written to /var/spool/lp, thus I am unable to print ANYthing. foomatic-1.1-0.20011218.3 printconf-0.3.44-1 I am using those versions.
You need to update printconf. If there are other problems with the updated printconf version, let's look at them; but problems with 0.3.44-1 aren't going to get fixed if they are already fixed in the update. So: what goes wrong with the newer printconf?
It is pretty simple. Run the printconf tui, configure a printer, save it, cd to /var/spool/lp, and it's empty. Try again, fire up printconf, configure again (as there is nothing there), this time try to test it, which involves a save first, nothing. It gets an error trying to print (due to the fact that there is no files in /var/spool/lp). This was effecting me a month or so ago, so if there was a recent update to printconf, I will try. It was my understanding though, that printconf was just the tool to configure the printer. The rest of the magic was done by the other packages.
Well, there is no directory /var/spool/lp on my set-up; do you mean /var/spool/lpd? This is working for me and plenty of other people, so the more specific you can be about what you are doing, the better. The /var/spool/lpd directory is provided by the 'filesystem' package. Did you delete that directory? Use 'rpm --verify filesystem printconf foomatic' to find out what things are wrong with the installation.
Sorry, it was /var/spool/lpd not lp. Anyway, I just tried again, with the newer printconf, no such luck. Removed the current printer, configured a new one (exactly the same), tried to test, and got the message of "Error Could not print the page" or something to that effect. Exited, and /var/spool/lpd is once again empty. If I rpm -e that version of printconf, and install the older version (original with 7.2), configure and test a postscript page, it works just fine. Oddly enough, I can print ascii pages from a win32 box, through samba (the printer is shared). If it helps, this is a Cannon BJC3000 using the 6000 driver, default options.
Please stick with the newer printconf, so that I know exactly what's going on. Once you have upgraded printconf, please show me the output of: rpm --verify foomatic printconf filesystem Then, please add the printer as normal, and attach /etc/alchemist/namespace/printconf/local.adl to this report. If you see an error message anywhere along the way, please say what says---I'll need to know the _precise_ wording so that I can find where it comes from. Thanks.
[root@anakin root]# rpm --verify foomatic printconf filesystem SM5....T c /etc/alchemist/namespace/printconf/local.adl .......T c /etc/alchemist/switchboard/printconf.swb.adl .......T c /etc/printcap.local Removed old printer, added new one, and just exited, and saved it when it asked me to save. No errors there. I will attach that file when I am done with this message. After the TUI is done, and I exit from 'setup', I cd over to /var/spool/lpd/ and do an ls. Here is what I get: [root@anakin lpd]# ls -al total 2 drwxr-xr-x 2 root root 1024 Apr 25 08:18 . drwxr-xr-x 10 root root 1024 Mar 9 09:17 .. [root@anakin lpd]# Nothing went there. SO! I fire up setup again, and go to printconf. It shows my printer there, but when I go to test it, with a US Letter PostScript Testpage, I get this error: There was an error trying to print the test page. In a ncurses window, with an OK box. Hit OK, exit the printconf (printer still shown as there), and exit setup. Once again, /var/spool/lpd is empty.
Created attachment 55304 [details] Requested file for debugging purposes
Thanks. Do you have mpage installed, by any chance? If not, please install it and see if that makes a difference.
Ok, now I can print a test page, and a test ascii page, and I can lpr foo (foo being an ascii file). Thank you. Might I suggest mpage being a dependancy of the print packages? Would save a bit of headache....
*** This bug has been marked as a duplicate of 59481 ***
I am still confused as to why printconf would not write out the configuration to /var/spool/lpd without the mpage package installed. Seems quite odd. I do see how making mpage be a dependancy would solve it, but that's kinda like a bandaid, not a resolution. *shrug* oh well.