Public bug reported:
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.
** Affects: snapcraft
Importance: Undecided
Status: New
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapcraft
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/1876798
Title:
subiquity service should not be running after install on classic
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1876798/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
