Hopeinen Omena M: Ms Office X For Mac
Problem: jobs can be printed from the command line, but no output appears when attempting to print directly from applications such as Preview or Microsoft Office. The problem is not the same as the `Word doesn't print' from which many people seem to suffer - Office is perfectly aware of the printer. Server: HP Deskjet attached to a Debian Woody machine (`vihta') running CUPS 1.1.14. Local printing works perfectly.
- Hopeinen Omena M: Ms Office X For Mac Free
- Hopeinen Omena M Ms Office X For Mac
- Hopeinen Omena M: Ms Office X For Mac Download
Hopeinen Omena M: Ms Office X For Mac Free
Cups is set up to be browsable from the LAN, with `Allow From LAN IP range' in the directive in cupsd.conf. Client: Mac OS X 10.3.2 (`omena') attached to the LAN. The remote printer appears in the Printer Setup Utility as `Deskjet default queue' under `Shared Printers', and `Show info' reveals that it is `locally attached' and is referred to as `lp@vihta'. In Safari, gives all the usual info on the queue, and I can print a test page. I can print PS and PDF files from the command line using `lpr foo.ps' or `lpr foo.pdf'.
I can also print from unixy programs such as Lyx and gv, which probably use lpr anyway. However, I haven't had any success printing from `native' OS X programs such as Office or Preview. I get a brief progress bar claiming that the job is `processing', but no job appears in the print queue window. I can successfully print to a PDF file which I can then print from the command line.
All jobs, whether they produce printed output or not, leave the following message in /var/log/cups/errorlog: I 04/Jan/2004:18:03:47 +0000 Job 23 queued on 'lp@vihta' by 'stephen'. I 04/Jan/2004:18:03:47 +0000 Started backend /usr/libexec/cups/backend/ipp (PID 2242) for job 23. Though the following message.sometimes. but not always appears for unsuccessful jobs: E 04/Jan/2004:18:03:53 +0000 getjobattrs: job #23 doesn't exist! On the server, all jobs - successful or unsuccessful - leave a trace in /var/log/cups/errorlog of the form I 04/Jan/2004:18:14:19 +0000 Job 44 queued on 'lp' by 'stephen'.
I 04/Jan/2004:18:14:19 +0000 Started filter /usr/lib/cups/filter/pdftops (PID 3393) for job 44. I 04/Jan/2004:18:14:19 +0000 Started filter /usr/lib/cups/filter/pstops (PID 3394) for job 44. I 04/Jan/2004:18:14:19 +0000 Started filter /usr/lib/cups/filter/cupsomatic (PID 3395) for job 44.
I 04/Jan/2004:18:14:19 +0000 Started backend /usr/lib/cups/backend/parallel (PID 3396) for job 44. So, something recognizable is reaching the print server, but this `something' produces no output when it originates directly from Preview or Office. Any ideas what's going on? Click to expand.Thanks for your reply. On the client, /etc/cups/ppd is empty, though there is a binary file /etc/cups/ppds.dat. I tried copying the lp.ppd file from the server to the client (as ) but with no difference in the result. I set LogLevel to `debug' as you suggested, and here are the lines from /var/log/cups/errorlog when I submit an unsuccessful job (note the clocks on the two machines appear to be about 30 secs out of sync).
Sorry for including so much material - I'm not sure how much might be relevant, as there's nothing in here that looks suspicious to me (the only error is a Locale problem, which appears to be benign). I've wrapped some of the longer lines of output. Click to expand.Assuming this is the log from the non-printing client, verify that this directory exists Don't know if it's fixed in Panther, I had a similar problem in 10.2 localhost:p% ls -la /var/spool grep cups drwx- 32 daemon admin 1088 Dec 16 11:43 cups so you will need to sudo or su to dig deeper In my case, for whatever reason, /var/spool/cups/tmp did not exist so the spool jobs were being dumped at /var/spool/cups where they couldn't be found.
Hopeinen Omena M Ms Office X For Mac
If the dir doesn't exist you can just create it there, chown & chmod localhost:/var/spoolp% sudo ls -la cups drwx- 32 daemon admin 1088 Dec 16 11:43. Drwxr-xr-x 12 root wheel 408 Oct 14 12:58. Drwx-T 3 daemon admin 102 Dec 16 11:43 tmp I didn't set the T flag, daemon must have done it later. Click to expand.I've appended such lines to the end of this message, for a job sent from gv on the one hand (uses ghostscript and lpr) and directly from Preview.app on the other. Output is similar to the lpr case if I print from the command line on the server, or lpr foo.pdf from the client file as the argument to lpr from the client.
Hopeinen Omena M: Ms Office X For Mac Download
The list of arguments is much longer when printing from Preview.app, so much so that the output in errorlog is clearly truncated. Successful jobs seem to have few enough arguments that there is no truncation. I don't know whether this could cause the error I see. The biggests difference in errorlog between successful and unsuccessful jobs is that I see lines of postscript for the former. When printing a PDF file, either via Preview or via lpr, the processes pdftops, pstops, and then cupsomatic run, but only for the command line jobs do I get a message `pdftops - opend PPD file /etc/cups/ppd/lp.ppd', followed by some postscript lines, then some PJL lines, then the converted file, then EOF etc. Click to expand.