I've decided to take the initiative and test the latest/edge branch of snapd snap, snapd 2.77+g71.94aa701, and can confirm this fixes the issue.
There are no more apparmor denies within the kernel buffer that pertain to network sockets being blocked as soon as I upgrade from the newly (current) released 2.76.3 version to 2.77. I made sure to remove the `SNAP_REEXEC=force` flag in /etc/environment for testing both the current and edge releases, and the bug persists on 2.76.3 and lower. $ snap debug execution apparmor apparmor-parser: /snap/snapd/28086/usr/lib/snapd/apparmor_parser apparmor-parser-command: /snap/snapd/28086/usr/lib/snapd/apparmor_parser --config-file /snap/snapd/28086/usr/lib/snapd/apparmor/parser.conf --base /snap/snapd/28086/usr/lib/snapd/apparmor.d --policy-features /snap/snapd/28086/usr/lib/snapd/apparmor.d/abi/5.0 internal: true $ snap version snap 2.77+g71.94aa701 snapd 2.77+g71.94aa701 series 16 ubuntu 26.04 kernel 7.0.0-30-generic architecture amd64 $ /snap/snapd/28086/usr/lib/snapd/apparmor_parser -V AppArmor parser version 5.0.2 Copyright (C) 1999-2008 Novell Inc. Copyright 2009-2018 Canonical Ltd. Glad I could be of service, although I am aware that I may be an edge case, but its probably a good idea to ensure that this fixes the particular bug for others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2154378 Title: Snaps lost internet access after updating snapd to 2.75.2 on Ubuntu 26.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2154378/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
