Public bug reported:
Hi,
Could the `daemon` app in the chromium snap get `restart-condition:
always`? It's a one-line addition; nothing else in the app's definition
needs to change.
**The problem**
The `daemon` app sets no restart condition (`snapcraft.yaml`, `stable`
branch, 158.0.8127.36), so snapd generates `Restart=on-failure`.
Chromium can exit cleanly, though. On a kiosk running r3555
(155.0.8059.39, arm64) we saw:
```
Fatal Wayland communication error: Connection reset by peer
```
followed by exit status 0 and "Deactivated successfully". A SIGTERM
counts as a clean exit too.
Either way systemd leaves the service down. On a kiosk the browser is
the whole UI: it runs full-screen on ubuntu-frame with no desktop or
launcher behind it, so the person at the touchscreen is left with a
blank screen and nothing to tap, and the only way back is to power-cycle
the device.
Anyone running the daemon as a kiosk can hit this. With shell access a
systemd drop-in papers over it. On a signed Ubuntu Core model that isn't
an option: there's no shell, and one strict snap can't add a drop-in to
another's unit.
**Side effects of the change**
None that we can find. The app is `install-mode: disable`, so it only
runs where someone has enabled it, and `snap stop chromium.daemon` is
still honoured (checked on systemd 255.4: a stopped service stays
stopped, and a killed one is back in about 3 seconds).
One trade-off: with `restart-delay: 3s` and systemd's default start
limit, a browser that dies on every start will loop every few seconds
without tripping the limit. For a kiosk we'd take that over a dark
screen, but you may want a start limit alongside it.
This is on Ubuntu Core 24, arm64. Happy to attach logs or test a build
from any channel.
Thanks!
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2175438
Title:
[snap] chromium.daemon stays down after a clean exit: add restart-
condition: always?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2175438/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs