[Xprint] Re: Hang with "-XpSpoolerType cups"

David Schweiger dvschweiger at web.de
Mon Jun 14 01:12:25 EDT 2004


xprint at mozdev.org schrieb am 09.06.04 00:46:37:
> 
> Hi
> avorop at mail.ru wrote:
> [snip]
>  > Another question is definetely about xprint. When experimenting, I
>  > decided to try option -XpSpoolerType cups. This resulted in deadlocking
>  > of the clients. Even xphelloworld was deadlocked. The printing was done,
>  > but I guess the socket was not closed after it, so the client was
>  > sitting there till the server was terminated. I do have CUPS running so
>  > I find this behaviour kind of strange. As far as I understand the
>  > default value for this option is 'bsd:cups'
> [snip]
> 
> I had the same sort of trouble but was able to fix it by specifying
> 
> *xp-spooler-command: /usr/bin/lp -s
> 
> in /etc/Xprint/C/print/attributes/printer
> 
> This suppresses console output from lp, so it looks like the output 
> (printjob ID) from lp is confusing Xprt somehow.
> 
> My setup:
> 
> Debian sarge, kernel 2.4.25 on a k7
> mozilla-browser 1.6-5
> cupsys-client 1.1.20
> xprt-xprintorg 0.0.9
> 
> The printer is a HP5550 on another machine running the CUPS server.
Can you make a stack trace from Xprt that we can see where it exactly hangs?
__________________________________________________________________
Zeigen Sie Emotionen mit der WEB.DE Bild-SMS! Das Bild ist gratis,
Sie bezahlen nur den Versand. http://freemail.web.de/?mc=021196



More information about the Xprint mailing list