Follow-up from one bounded observation on the same system: TCP connection to the existing loopback SOCKS5 proxy succeeded, and the SOCKS5 greeting was written successfully. Reading the greeting response then failed with EACCES (OS error 13; NetLog error -10), before target TLS or HTTP. No download event occurred.
The target request was traced through NetLog dependencies to its socket. AppArmor receive denials in the same observation window belonged to the same browser NetworkService process, but their source ports differed from the target socket. Therefore, those audit entries do not establish the direct cause of the target request's failure. Audit completeness is not guaranteed, and the root cause remains unconfirmed. The observation used a fresh temporary profile and Default NetLog capture, with no security-policy or system-network changes. The browser exited normally. No raw logs or screenshots are attached. Previously reported versions: Chromium 155.0.8059.79 (Snap revision 3560), snapd 2.77.1, AppArmor 4.0.1, kernel 6.17.0-1021-nvidia. Could you advise the smallest supported diagnostic step to attribute this specific read failure, while retaining AppArmor, sandboxing and certificate verification? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2171566 Title: [snap] ERR_ACCESS_DENIED with GNOME SOCKS settings and nearby AppArmor receive denials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2171566/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
