Hi, it might be that the "New-Stylus-Color-printer" driver does not create correct postscript. Try using the PostScript Color driver that comes with CUPS-PDF (or at least some driver that explicitely says "generic PS driver").
Since the PDF is correctly created if you call cups-pdf directly (on the commandline) with a PS-File the printer driver seems the obvious culprit. Volker On Sat, 2006-04-01 at 22:44, Mario Oyorzabal Salgado wrote: > Hi, i have make more test's for know about this problem :-P, i have made this: > > # /usr/lib/cups/backend/cups-pdf 1 tuxsoul "Test" 1 0 /home/tuxsoul/mozilla.ps > > I think so cups-pdf run with user tuxsoul, the result is a correct pdf file, > in > tuxsoul home, but if try to print since gedit or any gnome or gui, > application, > the result is the empty file, may be ¿is the communication between cups and > cups-pdf? > > I have install the driver for printer "New-Stylus-Color-printer" for using > cups-pdf, in my gnome enviroment. Sorry for skype this info =P. > > > > Volker Christian Behr wrote: > > Hi, > > > > from what I can see from the logfile, when printing as non-root GS returns > > the error code 256 - this usually means that the source file cannot be > > read. Please check whether the directory /var/spool/cups-pdf/SPOOL is > > readable for the group lpadmin. One thing you can try is removing the > > entire directory /var/spool/cups-pdf ... CUPS-PDF will re-create the tree > > with suitable permissions. > > > > Volker > > -- Volker Christian Behr Experimentelle Physik V (Biophysik), Physikalisches Institut Universitaet Wuerzburg, Am Hubland, 97074 Wuerzburg, Germany Office: Room F-069a +49-931-888-5766 (phone) +49-931-888-5851 (fax)
