> Looks to me like your current KDE isn't too happy with the config files > =66rom the older KDE. Run rm -rf ~/.kde* to verify this theory. If true, > you can then try to copy bits of your old KDE config you really can't do > without to the new one.
Thanks. I suspected that, but surely I would have the same problem if I backed up an entire directory (including all hidden files, like .kde) and restored it later? Probably the only important KDE config file is for KMail, as it includes the list of mailservers we connect to and their settings. > > > Google is no help, probably because I cannot phrase the search well enoug= > h. > > The answer is only as good as the question. As it's pretty impossible to > ask a useful question here, google isn't much good... Well, most hits (for the searches I did try) simply say to copy home directories verbatim, but I think that only applies when you have a consistent server environment. That is to say move the entire contents of the old server drive to the new server drive, or restore a user directory to a server that itself has been restored. In both of these cases the files are all consistent as they are snapshots of the same machine in time. I guess what I was looking for was some explanation or warning about not trying to restore a copy of a user's directory from machine A to a similarly configured machine B. Andy
