Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I see a lot of posts from people asking for help with Cups printing over samba but no answers. I am having the same problem.
I have an HP 2500c hooked to a RedHat 9 samba server with the CUPS print system.
I can print fine from the server.
I can print fine from my Linux client.
I can not print from windows clients. The print job shows up in the queue and just disappears.
The cups error_log says:
PID 6794 stopped with status 2!
I set the debug level from info to debug and get:
job does not start with Postscript %! thing at /usr/lib/cups/filter/cupsomatic line 485, <STDIN> line 1.
From looking at the cupsomatic script it appears that
"# Line zero should be postscript leader" means there shoudl be a "%!" at the beginning of the print job, and it's not there. I am using the PostScript drivers from HP (HP 2500C Series PS3).
That would have been a helpful topic, if it solved the problem. The thread you pointed out just offered a work around for Windows 2000 machines. We have no Windows 2000 machines, just Windows 98 and 2 or 3 XP. We need to solve the problem with CUPS printing over SaMBa, not work around it.
All that the mime.convs fix does is to allow print jobs to pass straight through the cups filtering system. If you have already configured a Windows, non-Postscript driver on the clients, then this is the necessary workaround.
If, however, you are trying to do what I am doing--installing PostScript drivers on the clients so that I can count pages accurately with the accounting, this fix is not sufficient. In theory, all my Windows clients should be able to send PostScript to cups, and cups should know how to handle it.
I have the same problem. My print jobs briefly appear in the Windows client print queue, then disappear, even though no printing has in fact taken place. I can print fine from the server using cups. Looking in my /var/spool/cups directory, there are several c000** files. (Which I assume were some sort of print-job-description file that never got deleted for some reason). But I have not found a way to know where in the chain this process is breaking down. The only thing remotely close to an error message I found in the /var/log/cups/error-log saying that cupsomatic filtering had broken (which I assume means that an unrecognized format was encountered??-- not a useful error message IMHO).
Even printing with the mime.convs fix doesn't work for me, of course, because I've got a PostScript driver trying to print to a non-PostScript printer.