Specific error: Test failed due to One or more processes failed sandboxing: defaultdict(<type 'list'>, {'dbus-monitor': ['missing euser']}).

Not really sure who owns this test, lhchavez@ could you take a look? Thanks

The test is doing its job: there's a service in stout that's not configured correctly.

https://chromium.git.corp.google.com/chromiumos/overlays/board-overlays/+blame/d13723854c36dbd4dd1e73d407c658e70605418f/overlay-stout/chromeos-base/chromeos-bsp-stout/files/rf-led-handler.conf#81

Assigning to the last person who touched that file.

This test is still failing on stout. 

Build: 10718.88.2, 68.0.3440.118 stable-channel

Golden Eye release: https://cros-goldeneye.corp.google.com/chromeos/console/qaRelease?releaseName=M68-STABLE-CHROMEOS-4

Also failing on M69 beta (10895.33.0, 69.0.3497.58) https://cros-goldeneye.corp.google.com/chromeos/console/qaRelease?releaseName=M69-BETA-CHROMEOS-2

I fixed the conf file a few months ago such that stout's LED lights up when bluetooth service is enabled. I do not touch sandbox and do not know what's wrong with sandbox though. Please find a security/sandbox people to take a look. Thanks!

As discussed offline, josephsih@ will do the work or find someone to do it.

As outlined in [1], what needs to be done is to invoke the `dbus-monitor` command of rf-led-handler.conf[2] in an unprivileged fashion. This can be achieved by running it with `sudo -u $USERNAME`.

1: https://chromium.googlesource.com/chromiumos/docs/+/master/sandboxing.md#user-ids
2: https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/fee82089fb9d4646ff018ba8c4c01dd331eae96c/overlay-stout/chromeos-base/chromeos-bsp-stout/files/rf-led-handler.conf#81

Still failing on M69 beta 10895.40.0, 69.0.3497.73 
https://cros-goldeneye.corp.google.com/chromeos/console/qaRelease?releaseName=M69-BETA-CHROMEOS-3