New issue
Advanced search Search tips

Issue 655878 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 631171
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Doesn't keep logged in status of Gmail, Facebook, etc. (maybe something to do with keychain?) in Linux Mint.

Reported by prograha...@gmail.com, Oct 14 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Log into Gmail.
2. Restart Computer.
3. No longer logged into Gmail.

What is the expected behavior?
I should remain logged into Gmail, Facebook, etc.

What went wrong?
Browser doesn't hold logged in status on sites.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Not sure, but recently started happening.

Does this work in other browsers? Yes

Chrome version: 53.0.2785.143  Channel: n/a
OS Version: Mint Sarah
Flash Version: Shockwave Flash 23.0 r0
 
Components: -Blink Internals>Network>Cookies
This is not Blink. Tentatively moving to Network>Cookies.
Labels: Needs-Feedback
Can you check in chrome://settings under "Privacy" > "Content settings..." > "Cookies" that it's set to "Allow local data to be set" instead of "Keep local data only until you quit your browser"?

Does this happen only when you restart your computer, or does it also happen if you quit and restart chrome (while staying logged in to your computer)?

Comment 3 by vabr@chromium.org, Oct 21 2016

Cc: cfroussios@chromium.org
Keychain is mentioned in the title -- what are the connections you see?

(Adding cfroussios@ who has been working on encryption in GNU/Linux recently.)
 prograhamme: Any chance you can response to the questions in c#2 & c#3?  We need your help to make progress on this bug.

Mergedinto: 631171
Status: Duplicate (was: Unconfirmed)
Sorry I missed this bug. This sounds like a duplicate of  issue 631171 . This was fixed in Chrome 55, which is in beta until December.

A workaround is to have your default keyring unlock automatically on startup, or to download Chrome beta and help us verify that the issue is resolved.

Sign in to add a comment