Issue metadata
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 descriptionUserAgent: 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
,
Oct 12 2016
,
Oct 12 2016
Issue 655195 has been merged into this issue.
,
Oct 12 2016
Saw multiple users reports, if its reproducible we need to get a fix for next M54 Stable release.
,
Oct 12 2016
Anything you need for more information?
,
Oct 13 2016
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.
,
Oct 13 2016
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)
,
Oct 13 2016
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.
,
Oct 13 2016
Thanks Bibin and wardvandriessche@. I am looping to the owner of issue 631171 for further inputs.
,
Oct 17 2016
This sounds like the same root cause as 631171, we should consider merging the bugs.
,
Oct 17 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by wardvand...@gmail.com
, Oct 12 201660.9 KB
60.9 KB View Download
123 KB
123 KB View Download
154 KB
154 KB View Download