From: Stephan Kosinski <stephan@logan.tv>
Subject: Re: Rushtop: autostarting in KDE
   Date: Fri, 10 Jul 2009 14:24:33 -0400

Greg,

	I found out. hanks for the Autostart clue.

Case closed.

Thank you.

Stephan.

Stephan Kosinski wrote:

Greg Ercolano wrote:

    Starting a new thread for this..

Stephan Kosinski wrote:

A quick question though since I propagated the new binary on my linux

stations rushtop is auto-starting at user login.

    Hmm, nothing in rushtop or the rush installers does any autostart
    type stuff.. at least not in my code.

    Possibly the GUI toolkit rushtop is using has changed some internals
    that makes it more compatible with window manager autostart stuff
    that it didn't have before.

    Do other tools autostart if you logout while they're running?
    ie. firefox, konqueror, clocks, etc?

Yes but only when the session has been saved with them running. That means at logout or when the user save is session manually

    Sounds like a feature of the window manager remembering what
    was running when you logout, and starting them again when you
    login.

    This stuff is likely saved in an ascii file in your ~/.kde directory,
    but by what mechanism I don't know.

    I'll check there

What is reaaly weird is that I was never able to do that with previous

binary even by saving the KDE session with rushtop running.

    Hmm, I don't know what could have changed in rushtop to do that.
    Nothing in the code to rushtop itself.. I don't know of any way
    to control it from the GUI toolkit's API.

Do you have any idea how to prevent rushtop to auto-start? Is it
related to my system or to the new binary?

    Try closing rushtop *then* logging out, then back in.
    I would assume it won't start then.

First thing I tried. Close rushtop, save my session, logout and login again... Rushtop is stubbornly coming back . :)

    I stopped using KDE a while ago; too many memory hungry daemons and
    menus kept moving around, and same to be said for gnome, so I
    standardized on a custom 'tiny' window manager that has no daemons
    and one menu that I defined. This way I can upgrade my workstation,
    but have the interface stay the same.

    However, I'll try bringing up KDE on one of my other systems to see
    if I can at least replicate.

    But I figure KDE's own docs on autostart stuff will give reason
    to how to control autostarting, and possibly even specifying
    exclusion terms.

Thank you for your help. I will keep on searching. It is not big deal to have rushtop autostarts, just I'd like to understand and know how to control it.

Have a nice weekend.

Stephan.