.xsession can work, if your subshell will give Sugar time to start,
then copy environment variables from the Sugar shell process, then run
sugar-launch.
Don't know a best awy. Some deployments have used an automatic start
activity.
--
James Cameron
http://quozl.linux.org.au/
Hey George,
You could:
1) modify the sugar shell to launch it... ie., doing something similar to
what was done for the welcome activity. Or...
2) use the sugar services stuff to launch the activity without having to
modify sugar.
I would go for the second option, and simply write a _very_
On Wed, Sep 16, 2015 at 05:47:17PM -0700, George Hunt wrote:
> Thanks for the hints about timing, and environment variables. I'm
> inclined to continue to explore .xsessions because I think I will
> have a better chance to manipulate the mate desktop from bash,
> rather than from python scripts
What is the best way to autoexecute the browser at system boot time? I
tried .xsession, and then I realized that there's a lot to learn about
Sugar, and asking for advice might be a more direct approach.
Can there be separate paths for Mate and Sugar?