GitLab

The ash service was being started twice because it was not marked as
a "singleton" service. Service connections with different user ids
could result in the service starting twice in the same process.

This caused CHECK failures in bluez::BluezDBusManager::Initialize
and desktopui_MashLogin to fail in the autotest lab.

Fix by marking the ash and ui services as singlton services, which
they should have been in the first place.

Bug: 836311
Test: existing autotest desktopui_MashLogin
Change-Id: I066692b19bb5d89c75e46c79675024740f42f844
Reviewed-on: https://chromium-review.googlesource.com/1026202Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553235}