On Sun, 2006-04-02 at 18:49, Martin-Éric Racine wrote:
> su, 2006-04-02 kello 11:21 -0500, Mario Oyorzabal Salgado kirjoitti:
> Volker Christian Behr wrote:
> > > it might be that the "New-Stylus-Color-printer" driver does not create
> > > correct postscript. Try using the PostScript Color driver t
su, 2006-04-02 kello 11:21 -0500, Mario Oyorzabal Salgado kirjoitti:
Volker Christian Behr wrote:
> > 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 expli
Hi i have install the "postscript color driver", and get pdf files correctly
cool =). No more empty files ;).
i don't think the last driver "new-stylus-color-printer" not create correct
postscript files why the last test in where need of postscript file, i make this
postscript file using "new-styl
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 t
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
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 t
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 d
Hi, i'm do the step's you send me, and the pdf file was create correctly for
user root.
Testing again with user tuxsoul don't using the steps you send me, to record the
log in the cups-pdf_log file, when a user print but not is root, and the pdf
file is create with 718 or 716 bytes empty.
You ca
Volker Christian Behr wrote:
>>From the directory listing I can see that the cups-pdf_log was not
> touched for 2 days by now, but there are enties in the error_log. Do
> those give any insight?
>
> Volker
>
I don't see nothing bad in the error_log file for know the problem, you can see
the file
>From the directory listing I can see that the cups-pdf_log was not
touched for 2 days by now, but there are enties in the error_log. Do
those give any insight?
Volker
On Wed, 2006-03-29 at 19:00, Mario Oyorzabal Salgado wrote:
> Volker Christian Behr wrote:
> > Ok, do we get a log-file by now (/
Volker Christian Behr wrote:
> Ok, do we get a log-file by now (/var/log/cups/cups-pdf_log)? This one
> cups-pdf should write at least even if the PDF creation fails.
>
> Btw.: are you using SELinux?
>
> Volker
>
> On Wed, 2006-03-29 at 03:43, Mario Oyorzabal Salgado wrote:
>
Nop, i'm not usi
Ok, do we get a log-file by now (/var/log/cups/cups-pdf_log)? This one
cups-pdf should write at least even if the PDF creation fails.
Btw.: are you using SELinux?
Volker
On Wed, 2006-03-29 at 03:43, Mario Oyorzabal Salgado wrote:
> Volker Christian Behr wrote:
> > Oops, sorry, my mistake:
> >
Volker Christian Behr wrote:
> Oops, sorry, my mistake:
>
> it must read: /etc/cups/cupsd.conf , not /etc/cups/cups-pdf.conf
>
> So, please check /etc/cups/cupsd.conf for the RunAsUser Statement and if
> there is none add the following line:
>
> RunAsUser No
>
> and restart CUPS.
>
> Volker
>
13 matches
Mail list logo
