Actually, ubiquity used to be on vt7, why is it ending up on vt1? start-ubiquity-dm should be starting on tty7...
With: kernel cmdline vt.handoff=7, <email address hidden>, <email address hidden>, Requires=getty.target, eding ubiquity-dm active_vt() function to just return int(7) => boot takes forever, ubiquity comes up on vt7. There are systemd messages on vt1 and can login on vt2-6. Horum, something is odd, plymouth should be on vt7 too.
Actually, ubiquity used to be on vt7, why is it ending up on vt1? start-ubiquity-dm should be starting on tty7...
With: kernel cmdline vt.handoff=7, <email address hidden>, <email address hidden>, Requires= getty.target, eding ubiquity-dm active_vt() function to just return int(7) => boot takes forever, ubiquity comes up on vt7. There are systemd messages on vt1 and can login on vt2-6. Horum, something is odd, plymouth should be on vt7 too.