subiquity snap being updated kills subiquity
Bug #1724411 reported by
Michael Hudson-Doyle
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
Fix Released
|
Undecided
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
By some sequence of events I don't understand, if a new version of subiquity is found and installed by snapd, the currently running one is killed and a shell session appears on tty1.
I think this is probably related to the snap.subiquity.
Related branches
lp:~mwhudson/livecd-rootfs/subiquity-stable-refresh-safety
- Steve Langasek: Approve
- Mathieu Trudel-Lapierre: Approve
-
Diff: 45 lines (+13/-3)3 files modifieddebian/changelog (+10/-0)
live-build/ubuntu-server/hooks/032-installer-squashfs.binary (+1/-1)
live-build/ubuntu-server/includes.binary/overlay/lib/systemd/system/subiquity.service (+2/-2)
Changed in subiquity: | |
status: | New → Fix Released |
To post a comment you must log in.
I think this (and bug 1724410) could both be mitigated by disabling snapd.refresh.timer and given the timeframe maybe that's the best approach to take.