I presume this is only happening in the arm64 desktop install because it
doesn't have the subiquity snap, correct?
I have some questions about the change, and please bear with me if these
are obvious, as I'm not familiar with the process of generating
installer images.
a) What in the changes added to livecd-rootfs makes these changes
exclusive to arm64? They are all under live-
build/ubuntu/includes.chroot.minimal.standard.live/*, is that only used
in non-subiquity installs?
a.1) If these changes are indeed also affecting other non-arm64
architectures, then the test plan should include them, unless it can be
demonstrated that testing in one arch is obviously enough (and granted,
we don't perform the SRU test plan in all architectures: I raised this
point only because of (a) above)).
b) You mentioned the autologin.conf file as not having any subiquity
reference, but removed it anyway, why? Because looks like it is using an
"ubuntu-server" user that doesn't exist, at least not in a desktop
(arm64)?
b.1) I presume this autologin is used in the virtual terminal during
text-mode installs (or even graphical ones) where you just hit enter and
get a shell. Shouldn't that be the ubuntu user? And what does it mean to
remove this file, will we still be able to open a terminal during
install, or will that stop working because there is no user with a
password set at all?
** Changed in: livecd-rootfs (Ubuntu Noble)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083554
Title:
error: snap "subiquity" is not installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2083554/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
