New issue
Advanced search Search tips

Issue 674283 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome uses the wrong user data directory over chrome remote desktop on Linux.

Project Member Reported by msw@chromium.org, Dec 14 2016

Issue description

Chrome uses the wrong user data directory over chrome remote desktop on Linux.

1) Connect to a remote linux machine with Chrome Remote Desktop.
2) Run chromium or a dev build on the remote linux machine.
3) Navigate to chrome://version
Expected: Profile Path is a subdir in /usr/local/google/home/msw/.config/chromium
Actual: Profile Path is /usr/local/google/home/msw/.config/chrome-remote-desktop/chrome-profile/test-user

While developing chrome[os] on linux over chrome remote desktop, I frequently get profile/extension startup crashes on local builds because of a bad user-data-dir(?) It would be nice if the default user data directory used over chrome remote desktop matched the default user data directory when running chrome locally.

Perhaps I'm doing something wrong, but supplying a --user-data-dir command line flag every time I want to run a binary built on the remote machine (to avoid the aforementioned crashes) is frustrating. Please help!
 
Components: -UI>Browser>Profiles
Labels: -OS-Chrome OS-Linux
Status: WontFix (was: Untriaged)
This is by design because because if you try to use the same profile directory for both the console session and the Chrome Remote Desktop session, whichever starts first will get all the windows--if you run Chrome in the other context, it will just print out "Created new window in existing instance".

It's controlled by the CHROME_USER_DATA_DIR environment variable, so if you just unset that you'll use the same profile in both contexts; just be aware that strange things will happen if you are also running Chrome on the console.

Sign in to add a comment