On Sat, 2005-11-05 at 01:24 +0100, Felix C. Stegerman wrote: > > This looks like bug #271001, so maybe I'm unnecessarily duplicating > this, but unlike said bug, I can reproduce this w/ all web pages I try > to print. Also, said bug is against xprt-xprintorg instead of xprint. > > I'm using CUPS w/ a HP Jaserjet 1100 and cups-pdf. Both printers work > fine when using postscript printing from firefox or mozilla, but > xprint segfaults when I try to print to "hp1100@:64" or "pdf@:64". >
When you say xprint segfaults, do you mean that Xprt is no longer running afterwards (no output from "ps aux | grep [X]prt") ? If that is the case, you could possibly pin it down further by running Xprt by hand under strace or gdb (although I think I've stripped out the symbols so the gdb backtrace would only have limited information unless we use an unstripped version). To get the command line options Xprt needs, just copy the normal version you get from the ps command above (when Xprt is still running). Does the segfault happen equally when you print to file (or use ps_spooldir or pdf_spooldir to ~/Xprintjobs) ? > I hope someone can fix this ... > Me too... :) Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
