subiquity service should not be running after install on classic
Bug #1876798 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| subiquity (Ubuntu) |
Confirmed
|
Undecided
|
Michael Hudson-Doyle | ||
Bug Description
subiquity service should not be running after install on classic
the subiquity.service that is generated by snapd is not good enough, and livecd-rootfs overrides a lot of it. But why not all of it?
Also when people install subiquity snap on classic systems the subiquity service is started, and keeps on crashing.
I've tried doing this:
cat snap/hooks/install
#!/bin/sh
# If not live installer media, disable subiquity on tty1
if [ ! -f /cdrom/.disk/info ]; then
snap stop --no-wait --disable subiquity
fi
but that fails with change is already in progress.
I wonder if there is any know-how in having snap manage service file, which is not started by default.
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #2 |
Revision history for this message
| Ian Johnson (anonymouse67) wrote | #3 |
| Changed in subiquity (Ubuntu): | |
| status: | New → Confirmed |
| assignee: | nobody → Michael Hudson-Doyle (mwhudson) |
| no longer affects: | snapcraft |
| no longer affects: | snapd |
To post a comment you must log in.
I'm not sure if there's a way to have a snapd manage a service file that doesn't run by default, I can't see what easily. We could have subiquity-service just sit there if there is no /cdrom/.disk/info file or something?