Firxiao, we've discussed this issue in our team call. Unfortunately,
while unbound's library binaries (libunbound8 and libunbound-dev) are in
main, the rest of its binaries (including the unbound binary itself) are
in universe. This doesn't appear to be a strong candidate for pursuing
MRE, so are going to hold off on that for now. (It's also unclear if
1.13.2 has been confirmed to resolve the issue for you - did you test it
(or Ubuntu 24.04) already and verify it does fix the problem?)
However, the severity of the issue does suggest this potentially be a
suitable candidate for SRU. An SRU would provide the discrete fix and
be deployed to all Ubuntu 22.04 users. Before action could be taken
towards SRU, however, it'd need either the patch pinpointed or steps to
reproduce identified (ideally both). If you want to pursue that, I'd
suggest first posting relevant logs and (sanitized) traces/dumps to this
bug report, so we can follow your analysis work. Maybe we will have
some suggestions. Null pointer bugs can be caused by a variety of code
errors, so if your stack trace differs from the one(s) mentioned
upstream, it's also possible you've discovered an entirely new bug...
Alternatively, as I mentioned in the previous comment, we could prepare
a PPA for you with the 1.13.2 build; this would not fix the issue for
all users, but would enable you to resolve the problem in your local
environment.
** Tags removed: server-triage-discuss
** Also affects: unbound (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080494
Title:
Hang in Unbound 1.13.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2080494/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
