Yes, those are basically the exact same steps as piboot-try-validate will perform in the case of successful validation (essentially equivalent to: mv current old, mv new current, echo good > current/state, but safer). Hence your system should now be in the "normal" state.
However, I'm concerned we haven't tackled the root cause here. Could you check whether the issue still occurs with the new kernel? To do so: $ sudo flash-kernel $ sudo reboot The flash-kernel call wipes the old/ directory, and (re-)installs the boot assets into the new/ directory with new/state set to "untested" (current is left alone as the fallback). The reboot should then double boot to test the new assets. If it fails again, I'd be interested to see the output of "journalctl -b -1". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2154627 Title: piboot-try-reboot.service fails: reboot command cannot connect to D-Bus at sysinit.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2154627/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
