I dug into the source and dependencies, and this seems most likely due
to libuv1, which checks /proc/version_signature in uv__kernel_version()
in noble and later. That would explain why this did not show up for
jammy. I'm not sure if this really causes any issues for named, but it
still seems reasonable to allow it to read the kernel version info.
** Also affects: bind9 (Ubuntu Questing)
Importance: Undecided
Assignee: Lena Voytek (lvoytek)
Status: Triaged
** Also affects: bind9 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: bind9 (Ubuntu Plucky)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Noble)
Status: New => Triaged
** Changed in: bind9 (Ubuntu Plucky)
Status: New => Triaged
** Changed in: bind9 (Ubuntu Noble)
Assignee: (unassigned) => Lena Voytek (lvoytek)
** Changed in: bind9 (Ubuntu Plucky)
Assignee: (unassigned) => Lena Voytek (lvoytek)
** Changed in: bind9 (Ubuntu Noble)
Importance: Undecided => Wishlist
** Changed in: bind9 (Ubuntu Noble)
Importance: Wishlist => Low
** Changed in: bind9 (Ubuntu Plucky)
Importance: Undecided => Low
** Changed in: bind9 (Ubuntu Questing)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2119320
Title:
apparmor error opening /proc/version_signature
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2119320/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
