Michele Calgaro via trinity-devel wrote:

Hi Emanoil, there are varioius ways apps are launched at startup. What is your settings for session management? Is the application open before you log out? Is it in the autostart manager?

The app is tdebluezauth - it is derived from KUniqueApplication. I think this is the problem, but I am not sure and I want to understand how this SM works

So this is how it should look like

$ ps -fax | grep -E "tdebl|obex" 20611 pts/1 S+ 0:00 | _ grep -E tdebl|obex 2929 pts/1 S 0:00 tdebluez 2930 pts/1 S 0:00 _ /usr/lib/bluetooth/obexd 20565 pts/1 S 0:00 _ tdebluezauth --nofork

But when I log out when I have it running like this and login again tdebluezauth starts from SM with something like

tdebluezauth -session 10dae8df69000158129630200000018890025_1596095977_105687

There is no autostart for tdebluezauth.

The other thing is that I think to remember, that KUniqueApplication is unique only when detached, but not when started with --nofork.

I tried this and that, I also tried using dcop, but everything was unreliable ... long story short, I find the way it is now good except this being started automatically. It could be acceptable, if I could create TQProcess out of it somehow ... I got lost finally and ask here for advise.

What would be the solution programmatically?

thanks

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

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

Michele, thank you - this was the ultimate programmatic solution. For the public (as you answered in private, or may be I did and it did not get to the list) the solution suggested (and working) was TDEApplication::disableSessionManagement()

Hi Emanoil, I didn't mean to answer privately... probably I pressed the wrong button.

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.

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

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

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

Does it mean remove the autostart.desktop?

In the autostart file in /opt/trinity/share/autostart folder, use a line like this:

X-TDE-autostart-condition=<your app rc file>:<group name>:<property to check>:false

The last value is the default to use if the autostart option has never been set (like new user profile or if the application was never run). For example, TDEPowersave (if installed) is autostarted by default. Then the user can choose to change the settings from its GUI.

X-TDE-autostart-condition=tdepowersaverc:General:Autostart:true

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