This may be specific to kevin, as it continues to work fine on Eve. I don't have a kevin handy, as I'm WF NYC, however. Does anybody know if it ever worked?

I cannot confirm that it ever worked.

This one was yet another seccomp failure. The pipe2 and fcntl64 syscalls were missing from seccomp/aarch64/wl_device.policy.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/crosvm/+/98ca995c395905a6fe9d9d6394399d5336ef2608

commit 98ca995c395905a6fe9d9d6394399d5336ef2608
Author: Zach Reizner <zachr@google.com>
Date: Tue Jul 24 04:04:37 2018

wl: add pipe2 and fcntl64 to wl_device.policy

These syscalls were added to the x86 policy when vfd pipe support was
added, but they were never added to the arm version, for whatever
reason. This is needed to keep crosvm from getting killed by SIGSYS
whenver the user copies to or from guest applications.

BUG= chromium:864218 
TEST=on kevin, copy/paste to/from gedit

Change-Id: Ibe385d50e367c362e911badd640bab2c98e07030
Reviewed-on: https://chromium-review.googlesource.com/1145876
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>

[modify] https://crrev.com/98ca995c395905a6fe9d9d6394399d5336ef2608/seccomp/aarch64/wl_device.policy

[Auto-generated comment by a script] We noticed that this issue is targeted for M-69; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-69 label, otherwise remove Merge-TBD label. Thanks.

Your change meets the bar and is auto-approved for M69. Please go ahead and merge the CL to branch 3497 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), kariahda@(iOS), cindyb@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/crosvm/+/9976613b4ce36da7c7c268c3806c211e44429eab

commit 9976613b4ce36da7c7c268c3806c211e44429eab
Author: Zach Reizner <zachr@google.com>
Date: Wed Jul 25 17:40:12 2018

wl: add pipe2 and fcntl64 to wl_device.policy

These syscalls were added to the x86 policy when vfd pipe support was
added, but they were never added to the arm version, for whatever
reason. This is needed to keep crosvm from getting killed by SIGSYS
whenver the user copies to or from guest applications.

BUG= chromium:864218 
TEST=on kevin, copy/paste to/from gedit

Change-Id: Ibe385d50e367c362e911badd640bab2c98e07030
Reviewed-on: https://chromium-review.googlesource.com/1145876
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>
(cherry picked from commit 98ca995c395905a6fe9d9d6394399d5336ef2608)
Reviewed-on: https://chromium-review.googlesource.com/1150302
Commit-Queue: Zach Reizner <zachr@chromium.org>

[modify] https://crrev.com/9976613b4ce36da7c7c268c3806c211e44429eab/seccomp/aarch64/wl_device.policy

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot