+levarum since I'm OOO today.

Looks like cryptohome issue again.
@apronin to confirm

[3399:3399:1216/225313.632586:ERROR:input_method_manager_impl.cc(1032)] IMEEngine for "jkghodnilhceideoidjikpgommlajknk" is not registered

DevTools listening on ws://127.0.0.1:45022/devtools/browser/e13a839c-f382-418f-b2f8-60c638a104e3
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[3399:3399:1216/225319.071574:ERROR:device_event_log_impl.cc(156)] [22:53:19.071] Login: homedir_methods.cc:274 HomedirMethods MountEx error (CryptohomeErrorCode): 1
[3399:3399:1216/225319.071677:ERROR:device_event_log_impl.cc(156)] [22:53:19.071] Login: cryptohome_authenticator.cc:932 Cryptohome failure: state(AuthState)=1, code(cryptohome::MountError)=32
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[1216/225321:INFO:policy_key.cc(51)] No policy key on disk at /home/user/9111cbbb3d8d602cfed6ef7d317865eee207c53f/key.pub
[1216/225321:INFO:keygen_worker.cc(46)] Generating Owner key.
[3399:3399:1216/225321.870741:ERROR:input_method_manager_impl.cc(1032)] IMEEngine for "jkghodnilhceideoidjikpgommlajknk" is not registered
[3399:3399:1216/225322.513918:ERROR:customization_document.cc(623)] Customization manifest is missing on server: https://ssl.gstatic.com/chrome/chromeos-customization/edgar.json
[3399:3421:1216/225323.179984:ERROR:owner_key_util_impl.cc(30)] Could not get size of /var/lib/whitelist/owner.key
[1216/225325:INFO:keygen_worker.cc(53)] Writing Owner key to /home/user/9111cbbb3d8d602cfed6ef7d317865eee207c53f/key.pub
[1216/225325:INFO:policy_key.cc(120)] wrote 294 bytes to /home/user/9111cbbb3d8d602cfed6ef7d317865eee207c53f/key.pub
[3399:3399:1216/225326.684335:ERROR:server.cc(1915)] Not implemented reached in void exo::wayland::(anonymous namespace)::remote_surface_set_rectangular_shadow_background_opacity_DEPRECATED(wl_client *, wl_resource *, wl_fixed_t)
[3399:3399:1216/225335.784569:ERROR:object_proxy.cc(626)] Failed to call method: org.chromium.Midis.BootstrapMojoConnection: object_path= /org/chromium/Midis: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.Midis was not provided by any .service files
[3399:3399:1216/225335.784654:ERROR:arc_midis_bridge.cc(65)] ArcMidisBridge had a failure in D-Bus with the daemon.
[3399:3399:1216/225431.311718:ERROR:server.cc(1915)] Not implemented reached in void exo::wayland::(anonymous namespace)::remote_surface_set_rectangular_shadow_background_opacity_DEPRECATED(wl_client *, wl_resource *, wl_fixed_t)
[3399:3399:1216/225431.317863:ERROR:multi_user_window_manager_stub.cc(17)] Not implemented reached in virtual void MultiUserWindowManagerStub::SetWindowOwner(aura::Window *, const AccountId &)

MountEx error lines in chrome logs are not necessarily an indication of an issue. I see the same lines for successful runs of that test. And they just mean that the test is run on a device where the local homedir for this user is not created yet, so it returns an error on the 1st attempt to mount an existing homedir, and then goes ahead and creates the user. 

E.g. here is the successful test: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/167039175-chromeos-test/chromeos4-row9-rack9-host2/cheets_MediaPlayerVideoHWDecodeUsed/sysinfo/var/log_diff :

[4451:4451:0102/081516.343339:VERBOSE1:gaia_screen_handler.cc(971)] LoadAuthExtension, force: 1, offline: 0
[4451:4451:0102/081516.344806:ERROR:device_event_log_impl.cc(156)] [08:15:16.344] Login: homedir_methods.cc:274 HomedirMethods MountEx error (CryptohomeErrorCode): 1
[4451:4451:0102/081516.344952:ERROR:device_event_log_impl.cc(156)] [08:15:16.344] Login: cryptohome_authenticator.cc:932 Cryptohome failure: state(AuthState)=1, code(cryptohome::MountError)=32
[4451:4451:0102/081516.345044:VERBOSE1:cryptohome_authenticator.cc(776)] Resolved state to: 6
[4451:4451:0102/081516.680231:VERBOSE1:signin_screen_handler.cc(1357)] Login WebUI >> loginVisible, src: oobe, webui_visible_: 0
[4451:4451:0102/081516.681155:VERBOSE1:webui_login_view.cc(633)] Login WebUI >> login-prompt-visible
[4451:4451:0102/081516.681284:VERBOSE1:arc_session_runner.cc(185)] Session start requested: MINI_INSTANCE
[4451:4451:0102/081516.681339:VERBOSE1:arc_session_runner.cc(258)] Starting ARC instance
[4451:4451:0102/081516.808157:INFO:signin_screen_handler.cc(1403)] Login WebUI >> active: 1, source: gaia-signin
[4451:4451:0102/081516.958286:VERBOSE1:gaia_screen_handler.cc(551)] Auth extension finished loading
[4451:4451:0102/081517.107195:VERBOSE1:cryptohome_authenticator.cc(776)] Resolved state to: 13
[4451:4451:0102/081517.107470:VERBOSE1:cryptohome_authenticator.cc(666)] Login success

So, so far doesn't seem to be a cryptohome error. However, I'd like to take a look at the full logs, just in case.
Could you please also point to the place where the chrome log from #2 was taken from - somehow couldn't find it for that test.

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

Looks obsolete. Feel free to reopen if that is not the case.