> Is this something we still need to fix in probert itself? I see that
https://github.com/canonical/probert/pull/152 was closed. Is this a case
where the fix makes sense, but verification is hard?
Actually, probert is no longer in the archive so there is no testing to
be done at the archive level. 22.04 was the last LTS where we had
probert in the archive. Since then we've been using "probert (Ubuntu)"
to track subiquity bugs that are related to probert - because there was
no "probert" upstream project on launchpad.
Maybe I'll create a probert project on launchpad in the future.
Either way, I'll mark the "probert (Ubuntu)" tasks as invalid. I suspect
~ubuntu-server could unsubscribe from this bug.
** Changed in: probert (Ubuntu Plucky)
Status: Fix Committed => Invalid
** Changed in: probert (Ubuntu Noble)
Status: New => Invalid
** Changed in: probert (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104087
Title:
segfault at 1 ip 0000761167255720 sp 00007ffd725da1a0 error 4 in
_nl80211.cpython-310-x86_64-linux-gnu.so
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2104087/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
