GitLab

Prior to this CL, files downloaded in Lacros would "disappear" -- they
would not show up in the file manager. The downloads code would choose
its default directory using the Chrome for Linux path provider, which
does not know about Chrome OS paths, and the files would end up in a
directory the file manager can't navigate to.

Add chrome_paths_lacros.cc to supply the correct paths.

Because Lacros does not support Chrome OS multi-signin, we make the
decision that lacros-chrome does not need to know about the under-the-
hood /home/chronos/u-{hash} multi-signin profile directories. It uses
the hard-linked /home/chronos/user path for the system primary profile.
This avoids exposing knowledge of the hash to Lacros.

Bug: 1139082
Change-Id: I8836760632fd9a1a8f9d49d7f03f1e6f6dfb0841
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500278Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821426}