Hemmann, Volker Armin posted <[EMAIL PROTECTED]>, excerpted below, on Wed, 28 Sep 2005 02:30:13 +0200:
> Hi, > > I removed the .kde* files/directories left from my earlier athlon-xp > installation and everything is fine now.f Thanks for reporting your fix. Of course, people like me get a bit frustrated with such reports, because we want to know /what/ /file/ caused the problem (we customize our KDE to the point where removing the entire customization, as this does, would be unthinkable), and once narrowed down to the file, preferably /what/ /line/ in the file caused the issue. I'm always copying the config to a backup, then removing half of it to see if the problem still exists, then either putting that back and removing the other half, or removing half of what remains... etc, until I reduce the problem to a single file and usually a single line within the file, when I suspect my config may be the issue. Of course, not everyone has the patience to do such things, but when the alternative is possibly days recustomizing things, as it can be for someone with a heavily customized config, a few minutes or hours spent isolating the problem to a single line in a single file is really the /easy/ way out! =8^) In any case, however, getting the feedback that the problem was solved, and that it was a config issue, is far more helpful than not ever knowing /what/ the problem was, so thanks for the fix report! -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
