Hi, I have no news because I was tied up with work and have not been able to try your suggestions. I am planning to do something about this issue over the weekend. I remember facing the same problem when I tried to print a PDF file from inside Acrobat Reader; again no problem when the file was opened with and printed from kghostview. One other thing I would like to mention is that at work I have set up a Linux server for a lab. It runs 64-bit OpenSuSE 10.2 on an Intel Core 2 Duo. I don't have any problem printing at work. Sure, the printer is different (Laserjet at work vs. my 8450 Inkjet at home), but my problems at home seem to be related to the arguments passed to and/or parsed by the foomatic filter, not with the PPD file. The major difference I see between the two machines (aside from the processors) is that on my machine at home I started with SuSE 9.1, then upgraded to 9.2, 9.3, 10.0, skipped 10.1 and, finally, upgraded to 10.2. On the machine at work, I started with OpenSuSE 10.1 and then upgraded to 10.2. So,I begin to suspect that something may have not been updated right on my machine at home, where I see the problem. Since I have access to the lab server at work, I will compare the configuration files for CUPS and foomatic-rip between the two machines, as well as firefox settings. Something has GOT to be different! CF Klaus Singvogel wrote:
Any news?
Regards, Klaus.
Klaus Singvogel wrote:
Constantine 'Gus' Fantanas wrote:
I am not sure whether I am dealing with a bug here, so before I bug bugzilla, I decided to post some new findings on this board. I activated logging of the foomatic-rip filter script. I printed a page I brought up with firefox into a file, then opened that file with kghostview, and from inside khostview I printed it; it came out perfect.
Sorry, but I miss some important information here. Which type of page did you open with firefox? I assume it's HTML, but you could also display PostScript or PDF or others...
Do you use any special printing options from firefox, when doing the printout? "special" means "non-default" values, like Input Slot (!), Quality/Resolution, page size, duplex, etc.
Do you print to the cups queue from firefox, or do you print via "foomatic" as printing command?
If you print using "foomatic-rip" (and not the cups tools), then you should change this, as you made an unsupported and not intended approach to print.
Test to print to queue "PostScript/default" and use your favorite printing command there (I'm using "xpp", but this is a matter of taste).
I then saved the /tmp/foomatic-rip.log' file as 'foomatic-log-kghost'. Then, I printed the very same page directly from inside firefox; I got the same garbage (the printer started printing Postcript commands in ASCII and I had to stop it to save some trees). I then saved the '/tmp/foomatic-rip.log' file as 'foomatic-log.str8' (when configured for logging, the foomatic script apparently uses the file '/tmp/foomatic-rip.log' and overwrites it with new data when its starts a new job). I have attached both files (which they will probably show up at the end of the thread).
Here are some salient points that I observed in the foomatic log files:
When I printed from inside firefox (job #207, garbage out), very few printer options were passed to the filter. The printer the foomatic script declared was 'foomatic-rip' and the printer model 'Raw que' (which agrees with the fact I got Postscript commands to print instead of being executed). What is very-very odd, foomatic reported the weird string "media=Letter job-uuid=urn:uuid:e1b70a11-685d-387a-6c55-7321d5932670" as a PPD file!!!!!! Something seems to be amiss here.
Yes, there is something wrong.
Can you please test to print PostScript files and textfiles from a console window, please?
Test for PostScript: lp -d <<printer>> /usr/share/ghostscript/*/examples/tiger.eps Test for textfile: lp -d <<printer>> /etc/aliases
I assume it's a problem in firefox.
In stark contrast, when I printed from inside kghostscript (job #206, which printed successfully), the foomatic script was passed on (or recognized) a lot of options and declared the HP8450 queue name; it also explicitly mentioned the PPD file (residing at '/etc/cups/ppd/HP8450.PPD'). Therefore, the PPD file I use for this printer is NOT the problem (or, at least, was not the problem when printing that page from inside kghostview).
The PPD file
What does kghostview do differently than firefox??? Why does foomatic get this weird string as a PPD file name when I try to print from inside firefox?
Yes, these are the right questions.
Could there be some error in foomatic, which causes the arguments passed to the script to be parsed incorrectly?
No, I doubt that this is related.
CF PS. I did visit < http://en.opensuse.org/SDB:CUPS_in_a_Nutshell > and found it very informative. In some cases it should mention /usr/lib64 for the 64 bit architectures. Also the URL < http://localhost:631/spm.html >, mentioned in the CUPS_in_a_Nutshell article, does not exist on my system (but the CUPS GUI at http://localhost:631 works fine).
The "spm.html" is still true for old SuSE distributions. But with switch to cups-1.2.x this is no longer true. The upstream maintainer, Michael Sweet, decided to no longer ship this file with his packages.
Thanks for the hint, we will note this loss in the document.
Regards, Klaus. -- Klaus Singvogel SUSE LINUX Products GmbH Maxfeldstr. 5 E-Mail: Klaus.Singvogel@SuSE.de 90409 Nuernberg Phone: +49 (0) 911 740530 Germany GnuPG-Key-ID: 1024R/5068792D 1994-06-27
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
-- Running 64-bit Linux on AMD64 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org