kdeprintd cannot start child process

[Nolan Rumble]

<snip>

Hmm... there shouldn't be such thing (most of the time, at least). I
migrated my configuration, little by little, since the time of KDE-3.0
(at least) and perhaps even since the time of KDE-2.0.

You might have had a KDE session interrupted by a crash or something,
which left some socket/lock file uncleaned and thus the dcopserver
unable to start automatically. This could happen (yet it shouldn't, I
acknowledge). In such cases, just remove the ~/.DCOPserver* files before
starting your KDE session (e.g. from a text console) and perhaps make
sure that the $KDEHOME/cache*
$KDEHOME/socket* $KDEHOME/tmp* symbolic links are pointing on existing
files/directories/sockets.

Hope this helps.

<snip>

I did remove all of those files from a text console.  It didn't work :(
...hence why I had to resort to moving $KDEHOME to another place thus
forcing KDE to recreate all the settings :)

Thanks for the help :)

Nolan