The `fwupd` SRUs for noble and jammy introduce two regressions: - Updating mtd devices crashes the daemon with a failed assertion (https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2156479) - BitLocker systems crash the daemon with a failed assertion (https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2156480)
This was detected in noble and phasing is at 0%; no jammy user has entered those code paths though. Our options are: 1. override phasing for jammy to 0% too; or 2. demote fwupd back to proposed I'm leaning towards 1, as the error cases are somewhat niche and people are _very_ interested in this update otherwise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2142578 Title: [SRU] fwupd backports for KEK and db updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2142578/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
