That's a long list of EPERMs in strace and mostly useless by itself, since chrome make use of nonblocking/asynchronous IO, so you always have to look for the syscall that had caused the EPERM. A full trace is rather huge.
In case you have a yubikey (not just a regular u2f oder blue yubikey, they don't show the problem) simply do something like strace -s 80 -f -o chromiumyubitrace chromium-browser --temp-profile https://demo.yubico.com/u2f ** Attachment added: "chromium_yubikey_EPERM.txt" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1825331/+attachment/5258943/+files/chromium_yubikey_EPERM.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825331 Title: apparmor chromium profile blocks yubikeys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1825331/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
