Implement boot-complete.target

Bug #1992643 reported by Julian Andres Klode
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Fix Released
Medium
Mate Kukri

Bug Description

systemd has a boot-complete.target that we should use to determine that boot has completed vs just being after basic.target. Custom checks can hook into that target to make sure the system is operational.

Related branches

Graham Inggs (ginggs)
Changed in grub2 (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
Revision history for this message
Mate Kukri (mkukri) wrote :

Adding the patch for this to the next Oracular upload.

Changed in grub2 (Ubuntu):
assignee: nobody → Mate Kukri (mkukri)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package grub2 - 2.12-1ubuntu9

---------------
grub2 (2.12-1ubuntu9) oracular; urgency=medium

  * Cherry-pick upstream efi mm patches to avoid crashing at exit on Mu
  * peimage: Improve section consistency checks, use grub_dprintf for errors
  * peimage: Make sure partially loaded images are unloaded on error
  * Implement support for UEFI NX mitigation
  * Cherry-pick missing TDX measurements fix (LP: #2069232)
  * grub-common.service: Add After/Requires=boot-complete.target (LP: #1992643)
  * d/postinst.in: Remove upgrade check for GRUB version we can no longer upgrade from
  * Cherry-pick fdtdump patch

 -- Mate Kukri <email address hidden> Wed, 19 Jun 2024 11:47:16 +0100

Changed in grub2 (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.