[Bug 2143048] Re: --restore-old thinks --reboot is always specified

Launchpad Bug Tracker 2143048 at bugs.launchpad.net
Tue Mar 3 01:21:49 UTC 2026


This bug was fixed in the package piboot-try - 1.1

---------------
piboot-try (1.1) resolute; urgency=medium

  * Fix operation of --restore-old (LP: #2143048)

 -- Dave Jones <dave.jones at canonical.com>  Mon, 02 Mar 2026 13:58:24
+0000

** Changed in: piboot-try (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to flash-kernel in Ubuntu.
https://bugs.launchpad.net/bugs/2143048

Title:
  --restore-old thinks --reboot is always specified

Status in flash-kernel package in Ubuntu:
  Invalid
Status in piboot-try package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Questing:
  Triaged
Status in piboot-try source package in Questing:
  Invalid

Bug description:
  From MM chat:

  $ sudo piboot-try --restore-old
  --restore-old --reboot makes no sense without --reset-new

  It appears --restore-old thinks --reboot is always specified even when
  it's not. This will need SRU'ing to questing as well (hence targetting
  flash-kernel as that's the location of piboot-try in that release).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2143048/+subscriptions




More information about the foundations-bugs mailing list