Michele Calgaro via trinity-devel wrote:

> TDEApplication::disableSessionManagement() may fix the issue, but you need
> to remember that in TDE different people may have different needs, so we
> need a way to let the users choose whether to launch the app at startup or
> not. If we just disable it, it is not the best solution.
> 
> We use TDEApplication::disableSessionManagement() when we don't want the
> application to be managed by the ksmserver, but in that case we provide a
> different way to control whether the application should start
> automatically at start up or not. This is done in two places: 1) the
> application has an option for autostart 2) there is an autostart script
> that look at that option and decide whether to autostart or not. You can
> look at TDEPowersave for an example and the relative script in
> /opt/trinity/share/autostart.
> 
> Just disabling session management without providing an option to the user
> is an incomplete solution IMO.

Thank you Michele for the time to write this explanation.
There is autostart configuration option already and autostart script for
tdebluez. tdebluez manages tdebluezauth, so I guess this matching perfectly
what you say.
Per default tdebluez is started automatically by the autostart script. The
user can then enable/disable the autostart. 
tdebluezauth itself does not have autostart script and session management is
disabled. The idea is, you either start it via tdebluez or you can start
manually on the command line - for whatever reason you want to do that and
use it as stand alone authentication manager.
tdebluezauth does not have a gui to control this behavior, but I think this
is OK - it is a helper anyway.

regards