App image autostart systemctl help

[bylosobie 0]

I don't know how I run it correctly . I manage to open the program at the autostart (using systemctl) add options like -password -login --network lock but what next?

The status shows me only "waiting for latency test 183 to go"

How to just connect to recomended server this way ? and network-lock is not working anyway
And why doesn't the GUI just start?

Edited ... by bylosobie

[OpenSourcerer 1359]

57 minutes ago, bylosobie said:

I manage to open the program at the autostart (using systemctl) add options like -password -login --network lock but what next?

Systemd is the wrong place to autostart a GUI app like Eddie. You must add it to the autostart mechanism of your desktop environment and tick the right config options in Eddie to engage NetLock automatically (or even connect). Don't bother adding arguments, they're part of the Eddie config saved in ~/.config/Eddie/default.profile.
 

57 minutes ago, bylosobie said:

And why doesn't the GUI just start?

If you start something as a Systemd service, it is launched with default User=root, Group=root options. Eddie might fall back to CLI operation because systemd/root doesn't run a DE and Eddie notices the absence of such, so the logs are posted to STDOUT/STDERR. Systemd-journald takes care of journaling that output and make it accessible for you via journalctl. I'm quite sure there are ways to make all that crap work via Systemd service, I could bump my fists against that wall; some time in the future it will crumble. But if an autostart entry in my DE will do the trick in the easiest way possible, the integrity of my fist bones becomes too important for me to lose.

[bylosobie 0]

18 hours ago, OpenSourcerer said:

You must add it to the autostart mechanism of your desktop environment a

thx, Can you tell how to do it on ubuntu then?

[OpenSourcerer 1359]

It's independent from the distribution. It depends on your desktop. GNOME, KDE Plasma, etc.