You can also make a custom script to get your apps loaded on boot
1. make a script, for example
/home/nemo/.config/systemd/scripts/autostart-apps
#!/bin/sh -
invoker -n --single-instance --type=silica-qt5 /usr/bin/sailfish-weather
invoker -n --single-instance --type=silica-qt5 /usr/bin/jolla-clock
#invoker -n --single-instance --type=silica-qt5 /usr/bin/jolla-email
invoker -n --single-instance --type=silica-qt5 /usr/bin/jolla-calendar
invoker -n --single-instance --type=silica-qt5 /usr/bin/harbour-amazfish-ui
invoker -n --single-instance --type=silica-qt5 /usr/bin/harbour-ownkeepass
invoker -n --single-instance --type=silica-qt5 /usr/sbin/harbour-privoxy --no-daemon /etc/privoxy/config.sailfish
-
since the 3.40-xx update, the jolla-mail refuses to start with the invoker instance, thats why I commented it. If anybody knows a fix, shoot…
-
edit: the email app seems tot start with:
invoker -n --single-instance --type=browser /usr/bin/jolla-email
2. make the script executable
chmod u+x /home/nemo/.config/systemd/scripts/autostart-apps
3. create a user service
/home/nemo/.config/systemd/user/autostart-apps.service
[Unit]
Description=Run applications at startup
Requires=lipstick.service
After=lipstick.service
[Service]
Type=oneshot
ExecStart=/home/nemo/.config/systemd/scripts/autostart-apps
[Install]
WantedBy=post-user-session.target
4. enable the user service
systemctl --user daemon-reload
systemctl --user enable autostart-apps.service