Me too: "Kprinter has stopped working - Unable to startchildprintprocess"

[Goffioul Michael]

> Thanks to David Faure, who answered my question on 
> kde-core-devel, we now know how to make this call on the 
> commandline. Here it is and also what is returned:
> 
> 
>   kurt@~> dcop kded kdeprintd print "ls -l" '(' 
> "/tmp/kdeprint.txt" ')' false
>   object not accessible
> 
> 
>   kurt@~> ls -l /tmp/kdeprint.txt
>   -rw-r--r--  1 kurt kurt 13 2007-01-29 17:32 /tmp/kdeprint.txt
> 
> 
> 
> And doing the same as root:
> 
> 
>   root:# dcop --user kurt --list-sessions
>   Active sessions for user /home/kurt :
>     .DCOPserver_soprano__0
>   
>   
>   root:# dcop --session .DCOPserver_soprano__0 --user kurt |grep kded
>   kded
>   
>   root:# dcop --session .DCOPserver_soprano__0 --user kurt 
> kded kdeprintd print "ls -l" '(' "/tmp/kdeprint.txt" ')' false
>   Xlib: connection to ":0.0" refused by server
>   Xlib: No protocol specified
>   
>   6119
>   
>   
>   root:# dcop --session .DCOPserver_soprano__0 --user kurt 
> kded kdeprintd print "ls -l" '(' "/tmp/kdeprint.txt" ')' true
>   Xlib: connection to ":0.0" refused by server
>   Xlib: No protocol specified
>   
>   6134
>   
>   
>   root:# ls -l /tmp/kdeprint.txt
>   /bin/ls: /tmp/kdeprint.txt: No such file or directory
> 
>   
> 
> Does this provide more clue now?

You should try a command that produces some result, in order to
check if it's actually executed. Maybe a "ls -l > /tmp/debug.txt"
can work, or even a "touch /tmp/debug.txt" (remove the file first,
"touch" should recreate it).

Michael.