Just a quick note, I found online a workaround to manually promote the new assets:
''' # Swap new firmware into current sudo gnumv -T --no-copy --exchange /boot/firmware/new /boot/firmware/current # Rename old new/ to old/ sudo mv /boot/firmware/new /boot/firmware/old # Set current firmware as good echo -n "good" | sudo tee /boot/firmware/current/state # Verify cat /boot/firmware/current/state zcat /boot/firmware/current/vmlinuz | strings | grep "Linux version" | head -1 ''' After this, I rebooted the system and the errors and the command 'piboot-try --status' return no response/empty which I assume it is now in a good state. -- 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
