Thanks Simon for confirming.
** Changed in: snapd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900679
Title:
[snap]
I've marked the chromium bug as invalid since snapd now allows
sched_setaffinity with browser-sandbox: true (see comment 16). I checked
here with firefox and chromium (both snaps) and the only syscall=203
denial is unrelated:
$ journalctl -o cat -b-1 -k --grep syscall=203
audit: type=1326
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900679
Title:
[snap] Apparmor audit messages for
It occurred to me that we don't actually currently have a way to silence
seccomp denials, so instead I opted to open a PR allowing unrestricted
sched_setaffinity with browser-sandbox: true @
https://github.com/snapcore/snapd/pull/9865.
Thanks for your patience.
** Changed in: snapd (Ubuntu)
Ubuntu 20.04.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900679
Title:
[snap] Apparmor audit messages for calls to sched_setaffinity
Status in chromium-browser
Ian is correct, all the explicit call sites for sched_setaffinity in
chromium are android-specific.
I do see a handful of those audit messages in my logs when I start
chromium, but it's far from spamming the logs. I wonder what is causing
such a volume for Avamander. Which OS/version are you
** Summary changed:
- [snap] chromium spams dmesg
+ [snap] Apparmor audit messages for calls to sched_setaffinity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900679
7 matches
Mail list logo
