autostarting but from where?
 

Hi ya all,
This tiny puzzle is driving me crazy!
This is what I did, installed gkrellm package that comes with fc3, ran it, configured it to my needs, and then added a .desktop link to it in /usr/share/autostart. Later I noticed that two instances of gkrellm were starting instead of one. After removing the link I made on /usr/share/autostart, only a instance of it is starting thats fine. But, I can't figure out from where it is starting. I checked the ususal locations, ~/.kde/Autostart and a few init scripts but couldn't find a clue. I'm not familiar with kde start up scripts/scripts locations. I even tried grepping gkrellm at different places(as per my knowledge) but couldn't find it.
So, I would appreciate if anyone could help me solve this mystery. Also, Is this autostarting of gkrellm a default behavior on fc3.

it could be in your kde session. If you stop it during your kde session, does it automatically restart when you log out an in

Oh! What a piece of shit I am.
You caught me in the balls Genixus. Thanks
I didn't know it was the session.
So enlighten me, how can I kill my session, after I log out of X.

Can you stop the gkrellm program before you log out of kde, then log out, then log in again? if you does it start then, even if you take the .desktop entry ou of autostart?

No no, Genixus, the puzzle is already sorted. I figured out it was the session after you pointed out, thanks.
So it doesn't load if it was closed at the last session.
I changed KDE session manager to "Start With Empty Session" instead of "Restore Previous Session" so its OK now.

But it would be handy if you could tell me, how to kill and or log in with a fresh session manually after logging out of X. I mean when "Restore Previous Session" is selected. Maybe I need to kill a process??!!

I really dout there's a way to do that, you might be abl to do some googling and figure out where that setting is saved, swtich to vty1 (ctrl + alt+ f1), log into console session, edit file switch back (alt+ f7) and the log in, but that's not something I'm familiar with.