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@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx 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
