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

[Kurt Pfeifle]

On Tuesday 06 February 2007 10:47, Andrew Myers wrote:
> Hi Kurt:
> 
> Did you manage to solve this problem or, if not, have you devised a work 
> around to print stuff from kde?

Sorry, no, not yet. I'll return later this afternoon to the machine 
in question; I'll still have to see what the result is of the last
test Michael had suggested to run.

> All the best
> 
> 
> Andrew
> 
> 
> Kurt Pfeifle wrote:
> > On Tuesday 30 January 2007 08:31, 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).
> >>     
> >
> > Good idea. But trying it only proofs in a different way, that the 
> > "dcop kded kdeprintd print" call fails:
> >
> >
> >   (a) if "/tmp/debug.txt" does already exist:
> >
> >       dcop kded kdeprintd print "touch" '(' "/tmp/debug.txt" ')' false
> >
> >       Error message pops up, see below (*) for its content.
> >
> >
> >   (b) if "/tmp/debug.txt" does already exist:
> >
> >       dcop kded kdeprintd print "touch" '(' "/tmp/debug.txt" ')' true
> >
> >       Same error message pops up, see below (*) for its content;
> >       however "/tmp/debug.txt" is indeed removed (as it should be,
> >       according to the "true" in the dcop call).
> >
> >
> >   (c) if "/tmp/debug.txt" does *not* already exist:
> >
> >       dcop kded kdeprintd print "touch" '(' "/tmp/debug.txt" ')' true
> >
> >       A warning pops up, see below (**) for its content.
> >
> >
> > Of course, for each of the tests, "/tmp/" and/or "/tmp/debug.txt"
> > were world readabable/writeable.
> >
> > ---------------------------------------------------------------------
> >
> > (*)  Content of error notification popping up: 
> >
> >      Headline says : "Catastrophe! KNotify"
> >
> >      Message is    : "
> >                       A print error occurred. Error message received
> >                       from system:
> >                       touch: execution failed with message:
> >                       touch: missing file operan Try `touch --help'
> >                       for more information.
> >                      " 
> >
> > ---------------------------------------------------------------------
> >
> > (**) Content of the warning popping up:
> >
> >      Headline says : "Warning - KDE Daemon"
> >
> >      Message is    : "
> >                       Some of the files to print are not readable by 
> >                       the KDE print daemon. This may happen if you 
> >                       are trying to print as a different user to the 
> >                       one currently logged in. To continue printing, 
> >                       you need to provide root's password.
> >
> >                       [ ] Do not ask again
> >
> >                       +-------------------------+        +--------+
> >                       | Provide root's Password |        | Cancel |
> >                       +-------------------------+        +--------+