kdeprintd cannot start child process

[Cristian Tibirna]

On 20 February 2006 15:04, Nolan Rumble wrote:
> <snip>
>
> Hi,
>
> I managed to solve my problem.  It seemed that settings from the
> previous version of KDE were conflicting with the new one.  I
> subsequently moved the .kde directory to .kde_back, thus forcing KDE to
> recreate all the settings.  Everything works now :)
>
> One question which I would like to ask is what is the bare minimum
> number of files that have to be deleted/changed in order to facilitate a
> version upgrade between older and newer versions?
>

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.

-- 
Cristian Tibirna
KDE developer .. tibirna at kde.org .. http://www.kde.org