Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
I'm trying to start Chrome in kiosk mode from a systemd service on boot. The 'webserver app' named 'xx' in the samples launches but chromium never comes up.
ExecStartPost isn't meant for starting long-running processes, so I guess systemd kills chromium-browser after /usr/local/xx/chromium.sh exits. You can see this by putting a sleep 10 at the end of /usr/local/xx/chromium.sh: Then Chromium comes up and gets killed after 10 seconds.
I don't know if you can "detach" Chromium enough that systemd doesn't kill it. But why not start Chromium from its own unit (with the correct ordering and dependencies)?