Reporter@ Thanks for the issue.

Tested this issue on Ubuntu 17.10 on the reported version 71.0.3578.80 by following the below steps.

1. Launched Chrome and logged into google.
2. Verified that the login is saved by exiting the browser and reopening.
3. Closed the browser and tried launching the browser from the terminal by giving the above command, but seeing error as attached in the screen shot.

Request you to check and confirm if anything is missed from our end in triaging the issue.
Also as this issue is related to Headless mode, adding appropriate component and labels and requesting the team to look into the issue and help in further triaging.

Thanks..

Deleted: 915543.png 134 KB

	915543.png 134 KB View Download

Hello, thanks for looking into the issue.

1-3 seem to be working fine for moth of us.  
4 works fine for me in Google Chrome 71 as in the screenshot attached.
I have verified step 5 using a remote debugger on a separate chromium 70 instance, also as shown in the screenshot.

Deleted: Screenshot_20181217_205738.png 159 KB

	Screenshot_20181217_205738.png 159 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

goldenvinay4@ Thanks for the update.

Retried the issue again on Ubuntu 14.04 using the Chromium build 71.0.3578.0 by following the below steps.

1. Launched Chrome and logged into gmail.com. Unable to Sign into Chrome and sync as this is not happening on Chromium build.
2. Verified that the login is saved by exiting the browser and reopening.
3. Closed the browser and tried launching the browser from the terminal by giving the command `chromium-browser --headless --remote-debugging-port=9222`, but seeing error as mentioned in comment #2.

As this issue is not reproduced at TE end, CC'ing owners from 'Internals>Headless' component and requesting Dev to look into the issue and help in further triaging.

Thanks..

You need to provide the --user-data-dir option to select the desktop chrome profile (by default, headless operates with an in-memory profile similar to incognito mode).

When you provide that flag pointing to the chrome profile directory, this should work for cookies. See discussion on  issue 617931  for more details.

The issue is present even when using the --user-data-dir option.

I followed steps 1-3 using the `--user-data-dir=chromeProfile`, where `chromeProfile` is a valid Chrome Profile in the current working directory.
Upon running step 4 using the `--user-data-dir=chromeProfile --headless --remote-debugging-port=9222` flags for google-chrome, and navigating to `localhost:9222` in a separate chrome instance, and remotely navigating , it is still showing up as if I am not signed in.

I have attached a screenshot showing the command I have used to open Chrome in headless mode. 

Deleted: Screenshot_20181219_200324.png 475 KB

	Screenshot_20181219_200324.png 475 KB View Download

Reopening, +caseq for triage.

This is fixed in 72.0.3582.0 by this change: https://chromium-review.googlesource.com/c/1274199