I suspect it was caused by a bad cl. vadimt@, could you help bisect on Eve to find the cl? 

FYI, from my fix yesterday on  issue 766876 , I've found that 9306235d959a38404e4a8614a60d77bccd4395ca is a good version. This broken CL is somewhere between that commit and ToT.

Looking

Still looking.
Looks like if you are quick enough to get past the network selection before the crash, the crash won't happen. This might unblock you while I'm looking at this.

I'm specifically trying to install Chrome on my Eve via deploy_chrome. When I deploy a new build, it fails to start up - can't really avoid this :(

OK, I've just done these steps:
export BOARD=eve && cros flash  --no-ping ssh://minnie xbuddy://remote/$BOARD/R63-9956.0.0/test --disable-rootfs-verification  --clear-cache --clobber-stateful

Deploy Chrome built from TOT (ebe5b1ca07e62ac237745ae27e5464d119bfce4e)
gn gen out_$SDK_BOARD/Release --args="$GN_ARGS" && git cl format  . && ninja -C out_${SDK_BOARD}/Release -j1000 chrome chrome_sandbox nacl_helper && deploy_chrome --build-dir=out_${SDK_BOARD}/Release --to=minnie

I'm seeing a "Welcome" screen, nothing crashes.

Do I need to do anything specific to get myself into the crashy state?

Hmm, are you performing this on a minnie? I see two mentions of "minnie" in your commands. This issue is on Eve.

It's Eve. minnie is just an IP alias.

vadimt@: I am still seeing this issue, but I'm on 9901.21.0 instead of 9956.0.0. Is that the issue?

Status:
I'm (Chrome on Cros gardener) still here, ready to take further steps to start bisection; currently I'm blocked on the question in comment 7.
Thanks!

#11 and #12 - race condition :)

Re#11: I suspect it may be the reason. I think you may need install a latest image and retry the simple chrome flow. 

Re #11:
Living with a too-old CrOS is a pathway to many problems some consider to be unnatural :)
Please try switching to 9956.0.0 and seeing if this solves the issue.
LMK the outcome; thanks!

Per  Issue 766876 , try ssh'ing in to print the ui logs:
localhost ~ # cat /var/log/ui/ui.LATEST
...
[25718:25718:0920/132305.061223:FATAL:cros_dbus_service.cc(76)] Failed to own: org.chromium.VirtualFileRequestService
#0 0x5edce00eb4dc base::debug::StackTrace::StackTrace()
#1 0x5edce01013ce logging::LogMessage::~LogMessage()
#2 0x5edce0ac4006 chromeos::CrosDBusServiceImpl::OnOwnership()
#3 0x5edcdf43091d _ZN4base8internal7InvokerINS0_9BindStateINS_17RepeatingCallbackIFvRKNS_8FilePathEbEEEJS4_bEEEFvvEE3RunEPNS0_13BindStateBaseE
#4 0x5edce00ebcd9 base::debug::TaskAnnotator::RunTask()
#5 0x5edce0107017 base::MessageLoop::RunTask()
#6 0x5edce0107816 base::MessageLoop::DoWork()
#7 0x5edce0109199 base::MessagePumpLibevent::Run()
#8 0x5edce0129d3a base::RunLoop::Run()
#9 0x5edcdfdf8d28 ChromeBrowserMainParts::MainMessageLoopRun()
#10 0x5edcde9f7fe4 content::BrowserMainLoop::RunMainMessageLoopParts()
#11 0x5edcde9fa792 content::BrowserMainRunnerImpl::Run()
#12 0x5edcde9f37bc content::BrowserMain()
#13 0x5edcdfdcc64c content::ContentMainRunnerImpl::Run()
#14 0x5edcdfdee87f service_manager::Main()
#15 0x5edcdfdcb511 content::ContentMain()
#16 0x5edcde352b35 ChromeMain
#17 0x75358ebcd736 __libc_start_main
#18 0x5edcde352919 _start

This pointed me at https://chromium-review.googlesource.com/c/chromium/src/+/662088
+CC derat and teravest@ are investigating.

+ovanieva@ RE #14 and #15
wrt tribal knowledge and the developer-pain saga: it would be nice if the 'deploy' tool would suggest updating CrOS to the latest green version, and if the user confirms, would flash that version.
Thoughts?

vadimt@ are you referring to functionality in GoldenEye? I'm checking with golden eye folks to see if we can do this. adding leecy@

Possible workaround: "killall -HUP dbus-daemon". (This seems to be doing something that rebooting the system doesn't!)

RE#19: I propose deploy_chrome cpmmand to automatically update CrOS to avoid installing newer Chrome builds on stale CrOS versions by devs. 

deploy_chrome just deploys Chrome. Deploying ToT builds of Chrome to a (slightly-) older OS is probably the main use of deploy_chrome, and I don't know of any way to tell whether the OS is too old to be able to run ToT Chrome. We generally aim for making ToT Chrome work with 1-to-2-week-old OS images, IIRC.

The problem discussed here isn't because the OS is too old. It seems to be an issue around dbus-daemon not picking up updated permission configs (which are pushed by deplay_chrome) for unknown reasons. I'm investigating and will file a new bug to track the problem.

vadimt@: I just tried with CrOS 9901.21.0, and I still get the same error.

Feel free to dupe this into  issue 767216 , if you want.

i tried tip of tree chrome on chrome os 63.0.3221.0, UI works fine. 

+1 to what derat@ said.

See also issue 767071 (no recent eve-release build) which is preventing Simple Chrome from updating the sdk (toolchain) it uses to build Chrome for Chrome OS. That doesn't sound like the problem here but seems worth noting.

FWIW I've been running recent Chrome builds with both oldish and new (as of this morning) CrOS images. I do get a message about restarting due to dbus changes but everything seems to be working OK.

RE Comment 24: Have you tried 9956.0.0, not 9901.21.0?
Happy to help, but are there any action items for me as a gardener, or should someone take this?

Oops, sorry about that. I copy-pasted the wrong version. I meant to say that I had just tried 9960.0.0 (even newer than 9956.0.0), but it didn't work.

If the root cause is  issue 767216 , let's dupe this into it.  

RE#29
I tried newer versions, and they crashed. Perhaps they have other issues, not sure.
The only version that worked for me was 9956.0.0.