Unlike installed desktops, we do not appear to be booting with vt.handoff=7 this is what should be putting plymouth on vt7, not switching and starting ubiquity there.
Similar to lightdm.service, I find that: Requires=getty.target; <email address hidden>; <email address hidden> => results in working tty2-6, only-ubiquity on tty1, and live session on tty7 (if e.g. one "quits" only-ubiquity). After=systemd-user-sessions.service would not hurt either, however, in practice, it is not needed, as that one starts whilst ubiquity is starting up/running.
Unlike installed desktops, we do not appear to be booting with vt.handoff=7 this is what should be putting plymouth on vt7, not switching and starting ubiquity there.
Similar to lightdm.service, I find that: Requires= getty.target; <email address hidden>; <email address hidden> => results in working tty2-6, only-ubiquity on tty1, and live session on tty7 (if e.g. one "quits" only-ubiquity). After=systemd- user-sessions. service would not hurt either, however, in practice, it is not needed, as that one starts whilst ubiquity is starting up/running.