PDF-Creation

[Eric SCHAEFFER]

Le lundi 04 octobre 2004 à 20:22 +0200, Karsten Fischer a écrit :
> Oh my--- I should have READ the fucking manual. Dumb me.
> Anyway, here is one way to solve this (at your own risk, of course, it
> might even break your system):
> 
> Browse through your /etc/cups/cupsd.conf and look for an entry
> 
> RunAsUser Yes
> 
> change Yes to No, restart cupsys and you should have a nice PDF-Printer.

A matter of user rights ?
Ok, it works for me too ;)

Eric

PS: no need to CC me, I receive list emails.

> Am Montag, den 04.10.2004, 19:50 +0200 schrieb Eric SCHAEFFER:
> > Le lundi 04 octobre 2004 à 19:34 +0200, Karsten Fischer a écrit :
> > > It seems I run into bad luck these days, I tried to set up a
> > > PDF-Printer. Setup was smooth, but everytime I try to use the
> > > PDF-Printer the printer is stopped.
> > > 
> > > The cups error-log says:
> > > 
> > > I [04/Oct/2004:19:31:43 +0200] Printer 'postscript-color-printer'
> > > started by 'root'.
> > > I [04/Oct/2004:19:31:43 +0200] Started
> > > filter /usr/lib/cups/filter/pstops (PID 12017) for job 3.
> > > I [04/Oct/2004:19:31:43 +0200] Started
> > > filter /usr/lib/cups/filter/foomatic-rip (PID 12018) for job 3.
> > > I [04/Oct/2004:19:31:43 +0200] Started
> > > backend /usr/lib/cups/backend/cups-pdf (PID 12019) for job 3.
> > > E [04/Oct/2004:19:31:44 +0200] PID 12019 crashed on signal 11!
> > > I [04/Oct/2004:19:31:44 +0200] Hint: Try setting the LogLevel to "debug"
> > > to find out more.
> > > E [04/Oct/2004:19:31:48 +0200] PID 12018 stopped with status 9!
> > > I [04/Oct/2004:19:31:48 +0200] Hint: Try setting the LogLevel to "debug"
> > > to find out more.
> > > I [04/Oct/2004:19:31:48 +0200] Saving printers.conf...
> > > 
> > > 
> > > anybody an idea how to get this straight?
> > 
> > No idea, but I've got exactly the same problem and cups output.
> > (debug level doesn't tell more about the problem...)
> > 
> > Eric
> > 
> > 
>