
It appeared with modern versions of Google's Chrome and Chromium web-browsers there was a dependency on Linux 3.17 or newer otherwise when dealing with Chrome extensions or apps there would be an error. It turns out that Google doesn't intend for there to be a hard requirement on the latest versions of the Linux kernel that expose SECCOMP_FILTER_FLAG_TSYNC but that many users are hitting an issue around it.
A Chromium developer commented on the related bug, "Updating the title so that people who have been mislead into thinking non-TSYNC kernels were deprecated immediately understand that there is simply 'some unknown bug' hitting some users."
The unknown bug though has yet to be figured out at the time of writing this article.
1 Comment