New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 655165 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

A change in your account requires that you sign in again

Reported by wardvand...@gmail.com, Oct 12 2016

Issue description

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

Steps to reproduce the problem:
1. Shut down computer
2. Restart computer
3. Open chrome/chromium browser

What is the expected behavior?
To be logged in automatically

What went wrong?
I noticed this behavior in Chrome a couple of weeks ago, switched to Chromium but today this started occurring too. I have to sign in to the browser every time I turn off my computer and restart.

Did this work before? N/A 

Chrome version: 53.0.2785.143  Channel: stable
OS Version: 14.04
Flash Version: Shockwave Flash 11.2 r999
 
Screenshot from 2016-10-12 17:01:39.png
20.0 KB View Download
Hi, after looking up a bit more I got this from: 
- terminal opening chrome (attachment no. 1)
- chrome://signin-internals when opening browser first time (attachment no. 2)
- chrome://signin-internals when logging in successfully (attachment no. 3)
Screenshot from 2016-10-12 21:25:59.png
60.9 KB View Download
Screenshot from 2016-10-12 21:27:29.png
123 KB View Download
Screenshot from 2016-10-12 21:27:50.png
154 KB View Download
Components: Services>SignIn
Labels: M-55 Needs-Bisect
Issue 655195 has been merged into this issue.
Cc: ligim...@chromium.org
Labels: -M-55 M-54 ReleaseBlock-Stable
Saw multiple users reports, if its reproducible we need to get a fix for next M54 Stable release.
Anything you need for more information?
Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Ubuntu 14.04 using chrome latest stable M54-54.0.2840.59 by following mentioned steps below.

1. Logged in to chrome using gmail account
2. Closed chrome
3. Restarted machine
4. Observed chrome logged in automatically as expected

There was a similar  issue 631171  related to Linux keyring where user is getting logged out from Gmail account automatically once restarting chrome, which got fixed recently. Not sure is this is the same root cause for it.

wardvandriessche@ - Could you please recheck this issue on chrome latest stable #54.0.2840.59 and kindly update the latest behavior of the bug.
brajkumar@ 

1. Updated to 54.0.2840.59 beta	
2. Set up google chrome (attachment no 1, attachment no 2)
3. Restart machine
4. Start google chrome beta from terminal (attachment no 3, attachment no 4)
5. Forced sign in (attachment no 5)
Screenshot from 2016-10-13 10:20:21.png
39.2 KB View Download
Screenshot from 2016-10-13 10:20:52.png
147 KB View Download
Screenshot from 2016-10-13 10:24:19.png
326 KB View Download
Screenshot from 2016-10-13 10:23:55.png
136 KB View Download
Screenshot from 2016-10-13 10:24:45.png
153 KB View Download
Update. "Fixed" the problem.

Noticed strange behavior in Gnome keyring: attachment no. 1
All logins had same information.

Steps I undertook:
1. Remove everything from chrome/chromium 
2. Remove ./.config/chrome ./.config/chromium
3. Remove ./.local/share/keyrings (all the duplicate)
4. Reboot machine
5. Open seahorse
6. See only 1 login password and change password to 'empty'
7. Installed chromium
8. Logged into chromium
9. Reboot machine
10. Started chromium and automatically logged in
11. Open seahorse and see only 1 login password, no duplicates

It seems chrome/chromium has troubles with encrypted gnome keyrings. I do not know more about this as I'm no expert. Questions are always welcome though.
Screenshot from 2016-10-13 10:59:33.png
23.8 KB View Download
Cc: cfroussios@chromium.org
Thanks Bibin and wardvandriessche@. I am looping to the owner of  issue 631171  for further inputs.
Owner: cfroussios@chromium.org
This sounds like the same root cause as 631171, we should consider merging the bugs.
Mergedinto: 631171
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment