-----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
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting