Public bug reported: Hi,
Plucky uses login(1) from util-linux instead of shadow, which means that utmp will not be updated anymore. This is what systemd's runlevel shim uses to determine the current runlevel, so from Plucky onwards running "runlevel" will return "unknown". "uvt-kvm wait"'s remote-wait-script relies on runlevel to determine whether the virtual machine is ready, and when executed against a Plucky VM the script will enter an infinite loop waiting for "runlevel" to return a valid output. The script needs to be updated to take into account systemd systems. I am locally relying on "systemctl get-default", but I'm not sure if it's enough. Debian's autopkgtest project also had to deal with this problem, and this is what they did: https://salsa.debian.org/ci-team/autopkgtest/-/commit/677af48 Maybe "systemctl is-system-running" is more trustworthy. ** Affects: uvtool (Ubuntu) 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/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs