1 |
Hemmann, Volker Armin posted |
2 |
<200509280230.14358.volker.armin.hemmann@××××××××××××.de>, excerpted |
3 |
below, on Wed, 28 Sep 2005 02:30:13 +0200: |
4 |
|
5 |
> Hi, |
6 |
> |
7 |
> I removed the .kde* files/directories left from my earlier athlon-xp |
8 |
> installation and everything is fine now.f |
9 |
|
10 |
Thanks for reporting your fix. |
11 |
|
12 |
Of course, people like me get a bit frustrated with such reports, because |
13 |
we want to know /what/ /file/ caused the problem (we customize our KDE to |
14 |
the point where removing the entire customization, as this does, would be |
15 |
unthinkable), and once narrowed down to the file, preferably /what/ /line/ |
16 |
in the file caused the issue. I'm always copying the config to a backup, |
17 |
then removing half of it to see if the problem still exists, then either |
18 |
putting that back and removing the other half, or removing half of what |
19 |
remains... etc, until I reduce the problem to a single file and usually a |
20 |
single line within the file, when I suspect my config may be the issue. |
21 |
Of course, not everyone has the patience to do such things, but when the |
22 |
alternative is possibly days recustomizing things, as it can be for |
23 |
someone with a heavily customized config, a few minutes or hours |
24 |
spent isolating the problem to a single line in a single file is really |
25 |
the /easy/ way out! =8^) |
26 |
|
27 |
In any case, however, getting the feedback that the problem was solved, |
28 |
and that it was a config issue, is far more helpful than not ever knowing |
29 |
/what/ the problem was, so thanks for the fix report! |
30 |
|
31 |
-- |
32 |
Duncan - List replies preferred. No HTML msgs. |
33 |
"Every nonfree program has a lord, a master -- |
34 |
and if you use the program, he is your master." Richard Stallman in |
35 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
36 |
|
37 |
|
38 |
-- |
39 |
gentoo-amd64@g.o mailing list |