Thanks. LP: #2165917 was found to be flawed in stonking, and is not yet
backported to resolute, so we should address both of those
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: subiquity (Ubuntu)
Milestone: None => ubuntu-26.04.2
** Also affects: subiquity (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: subiquity (Ubuntu Stonking)
Importance: Undecided
Status: New
** Changed in: subiquity (Ubuntu Stonking)
Milestone: ubuntu-26.04.2 => ubuntu-26.10
** Changed in: subiquity (Ubuntu Resolute)
Milestone: None => ubuntu-26.04.2
** Changed in: subiquity
Status: New => Confirmed
** Changed in: subiquity (Ubuntu Resolute)
Status: New => Confirmed
** Changed in: subiquity (Ubuntu Stonking)
Status: New => Confirmed
** Changed in: subiquity (Ubuntu Stonking)
Assignee: (unassigned) => Olivier Gayot (ogayot)
** Changed in: subiquity (Ubuntu Stonking)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2170594
Title:
accepted-errors: running-in-vm not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2170594/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
