Didn't get any response on this, so I kept on digging. Finally found the file /home/rudder/.kde2/share/config/ksmserverrc was launching the single KNode process, along with an unwanted instance of Konquerer, through something called restartCommand=. Most of the entrys in this file were in groups of eight. There were eight restartCommand commands, all with session IDs, but only three appeared to be actually being launched--the corrupt KNode process, Konquerer pointing to www.syse.com, and a single KNote process. I renamed the file so that KDE can't find it, and everything is working fine now. Apparently this is the config file for ksmserver, which I believe is the KDE session manager server. It must have somehow become corrupted. Anyway, the problem seems to be solved--for now anyway. Rudder
I'm having a minor problem with KNode. It doesn't want to load properly. Here's what's happening:
After I click on the KNode menu selection, I get a brief "loading application" icon in the taskbar, but it quickly disappears, and no window has KNode running.
Opening KPM finds a single sleeping KNode process with a session ID (really long hexadecimal number) grafted onto the command line.
If I send a terminate signal to the process, it dies and I can then launch and use KNode normally. BTW, when KNode is running normally, it has several processes, none of which have a session ID.
After closing KNode, KPM shows no KNode processes. Yet after a normal shutdown and reboot, the single KNode process with the session ID is back--and I have to terminate it to launch KNode.
The problem seems to have cropped up after I upgraded to KDE 2.1.2.
I've also noticed that KWin and KNotes have processes with session IDs, even though I've never used KNotes.
I searched the KDE site and didn't find any reference to this behavior. Anyone else run into this?