-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> 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.
>

Great, then it should be good :-)
I would suggest the default choice (on a new user profile/system) is NOT to start tdebluez automatically. The user can
then decide whether to autostart it or not. Reason for this is to be non-intrusive, since perhaps many users may not
use bluetooth at all.
Cheers
  Michele
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl8lNrEACgkQKnW3yore
1c8GhxAAnLa764gQrxCun0e2zP5FhMzIeJ+c22IRZFzkhSoJvrPsIDMOY/I1cI1n
5Wfn47HxQhbk044XIhrz9nrbumxfED7C1YfvaVKCEP8luNHXjm7oQ0d++XRv0cpu
h+0fU0dtZXxyH3zyI1i8w59jpEFOVTED3n4JiMb69UfmZSaom7ZUEx2EziYwLwwf
Nwtiwbmv45dotEdJ8TktVtlTq0CVs+yUp0NuWIwd7ruTAuHFbAQPhFUfu1aeIg2n
WBxR/SBPkdUf6lB4C1cCBuSZehdtJ/xow17Fc980clIWqrq/OMw3cWGx3bUZUHFh
URaVFmQ6Mr4K8wu7xooIZ0bDIcWyxb8HNvwh9OBsL3q8mtoFUyi5XOiIA2rxOTNx
4KVR48f6/1f22yEgxT3iSO/7ZSfEG8LQOUqOMPlMru/WyHy5zLAATGgTZloebtwR
VNDbs9c1tkpay7qE5tE6CmV0dVt+v4A9uMSZoYMwfbdhGjyNA/DAfFdjFAodMG5y
n42JeSpopuV4/Q5tB2p7DWOQThOx7qN+2Q6Va5onRxS8IYrCK+bI/cq8pZ2puWzo
/UL1dEza0mlUBsrfAdYBDG3aaDhZCoqAxcpntnUfGcYERRRp9QTnWz91Eak2Pn9d
6WJuUt7a0Fo84QeMlTIZNlPXFze/PlPHi9qI34zrWdhh64buxis=
=W+RQ
-----END PGP SIGNATURE-----