> /home/<user>/.kde and eventually deleted the whole folder, trying to make
> Knode forget that this user had ever started it before. In the end I
> reinstalled KDE's networking package but none of this has worked.
After you nuked everything like that, it should have taken care of the
problem for sure if it were any sort of typical KDE residual config file
issue... But your problem is as relates to running KNode from GNOME, so
you have introduced unfamiliar variables into the equation.
Before doing anything else, I'd suggest that you take another look at /tmp.
Are you _positive_ there isn't some lingering dotfile in there that's
causing your trouble? My usual way of deal with /tmp is to just nuke it
and make a new one. Make sure it has 1777 permissions.
Beyond that, I don't know. This is a *e to diagnose over the phone.
If I poked around on your computer, I might see something, or I might not.
Since I can't poke around on your computer, you're going to have to do it.
The fact that it's only happening to user X and not user Y indicates that
it's a problem with user X's configuration. You can all but eliminate
everything on the other side of the /home divide from consideration.
Re-installing KNode/kdenetwork is probably pointless.
It _could_ be some weird thing in /etc. If your distro has an
/etc/profile.d setup, maybe your user isn't running a script there that's
supposed to set up his PATH or something. I can think of a few scenarios
where that might be the case, but that's a pretty thin reach.
If KNode is working for user Y, then user X's configuration is screwed up
somewhere. Since it isn't any of the ~/.kde files, it has to be something
else. Did you delete... Um...
for f in `ls -a ~|grep -i cop`;do rm $f;done
Try running that again. If you still don't stumble your way into joy, then
I can't think of much else to try except a systematic process of trial and
Start by comparing the two users' environments. In bash, you can issue a
set command to see what's what. Log in as user X, then do something like
set > /tmp/userX.environment
Repeat for user Y, then diff the two files to point out all the differences.
You might notice something with the PATH or some other environmental factor
If that still doesn't get you there, perhaps you could make a copy of user
X's ~ under some temporary dummy user account, and then start deleting
stuff (dotfiles and dot-directories) and trying KNode again and again until
you stumble onto the thing that was causing you trouble.
Um... My final thought is one of permissions. Did you somehow end up with
a configuration file that you don't own? You might chown everything to
yourself just in case...
OK, that's all I can come up with... Good luck!
Michael McIntyre USDA zone 6b in SW VA, USA
---------========[Does your ls -O?]=======---------