Comment 3 for bug 1825331

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