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

[Andrew Myers]

As we have both found, printing from root works, but not from user. Here 
are the messages from a command line session:

[root at ezcool tmp]# kprinter N_L\ Collano\ Commission.jpg
kbuildsycoca running...
DCOP Cleaning up dead connections.
kprinter: WARNING: KGenericFactory: instance requested but no instance 
name or about data passed to the constructor!
KWrited - Listening on Device /dev/pts/4
[root at ezcool tmp]# exit
exit
[andrew at ezcool tmp]$ kprinter N_L\ Collano\ Commission.jpg
[andrew at ezcool tmp]$

See the absence of any messages from kbuildsyscocs, DCOP, kprinter and 
KWrited after invoking kprinter as user.
The root session printed fine, the user session failed with the usual 
error message.

All the best


Andrew


Goffioul Michael wrote:
>> 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.
> _______________________________________________
> kde-print mailing list
> kde-print at kde.org
> https://mail.kde.org/mailman/listinfo/kde-print
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-print/attachments/20070130/af7efe17/attachment.html