The relevant syscall is `sched_setaffinity`, which when used with a
first argument of `0` is allowed in the default policy. Can someone who
is experiencing this bug run an strace to determine what argument
chromium is trying to use with sched_setaffinity ? We allow any
sched_setaffinity arguments with the process-control interface, but if
this denial is not breaking the application then perhaps it should just
be silenced in the policy instead.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900679
Title:
[snap] chromium spams dmesg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
