<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>RE: kprinter polling</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>
<P><TT><FONT SIZE=2>> -----Original Message-----<BR>
> From: Frank Siegert [<A HREF="mailto:hugelmopf@vodafone.de">mailto:hugelmopf@vodafone.de</A>]<BR>
> Sent: Wed 12/1/2004 5:55 PM<BR>
T> o: For users and developers of KDEPrint, the KDE printing architecture<BR>
> Subject: Re: kprinter polling<BR>
> <BR>
> I have a new fact:<BR>
> When I print via the "lp" command instead of the "kprinter" command, it does<BR>
> not request a connection, although it uses CUPS as well and prints fine.<BR>
><BR>
> (Isn't this a challenge ;-))<BR>
<BR>
Are you sure you looked into the *correct* kdeprintrc and kprinterrc ??<BR>
And not an old one, which is't used any more? (See, sometimes an upgrad<BR>
from KDE-2.x to KDE-3.x may leave over the old $HOME/.kde directory and<BR>
the new $KDEHOME may be now named $HOME/.kde3....)<BR>
<BR>
Test it by changing a setting from the kprinter GUI, and then check<BR>
if it gets written into the file.<BR>
<BR>
Next, try to start kprinter from a konsole window and see if you<BR>
get any output on stdout (may not be the case, if stripped of all<BR>
debugging symbols).<BR>
<BR>
Then, you could try to run it under "strace" from console.<BR>
<BR>
* "strace -eopen kprinter" shows you all files kprinter attempts to<BR>
open. See if there is any network path amongst the verbose output.<BR>
* "strace -e trace=network kprinter" to trace all the network related<BR>
system calls. See if that gives some hint.<BR>
* "strace kprinter" shows all system calls kprinter makes. See "man<BR>
strace" for more detailed explanations and hints, if you are not<BR>
afraid of it. (Actually, the strace manpage is one of the better<BR>
ones, providing even examples, yay!)<BR>
<BR>
Last, you can try to the highly secret "kdebugdialog" (Psst!.... never<BR>
tell anybody it exists. I have a plan to sell a few dozen title stories<BR>
to PC Magazine and PC World and the like, once we dominate the desktop,<BR>
which all have variants of the one and only headline "50 more secret<BR>
KDE power tools revealed".) "kdebugdialog should pop up a GUI, which<BR>
lets you select which applications should give debugging output and<BR>
which ones not. If you have the same version as I have, you should<BR>
checkbox "500 kdeprint". (The line on top lets you search via partial<BR>
strings.). Run also "kdebugdialog --help" and "kdebugdialog --fullmode"<BR>
to see if it helps.<BR>
<BR>
> I'd rather keep printing via kprinter though, because it allows for more<BR>
> options (two pages on one etc.) :-)<BR>
<BR>
That's the only reason why you get help here :)<BR>
<BR>
But, hey, the two pages on one sheet is possible from the CUPS<BR>
commandline:<BR>
<BR>
lp -d printer -o pages-up=2 /path/to/file<BR>
<BR>
;-) ;-)<BR>
<BR>
> Frank<BR>
<BR>
Cheers,<BR>
Kurt</FONT></TT>
</P>
</BODY>
</HTML>