Issue metadata
Sign in to add a comment
|
Unable to log into google account
Reported by
jesse.m...@gmail.com,
Jun 12 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3457.0 Safari/537.36 Steps to reproduce the problem: 1. enter https://inbox.google.com 2. enter username 3. enter password 4. get error display dialog with the following message " Something went wrong Sorry, something went wrong there. Try again." With a Next button. It continue in the loop. 5. Can execute the same in the incognito window and I am successful at logging in. What is the expected behavior? In the default browser page it should be successfully logging in the same as it happened before the update to this version. What went wrong? I updated the chromium to the latest version, which I have been doing on a daily basis. I had this happen on my Windows 10 Pro build, and just figured it was a Microsoft issue due to I am running the fast track software for Windows 10. But on my work computer I run Windows 7 Pro with all the updates. Did this work before? Yes 565957 Chrome version: 69.0.3457.0 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: It would be nice if this could be figured out why it happens.
,
Jun 12 2018
In incognito window it is possible to sigh in to the google account without problems.
,
Jun 12 2018
I have uninstalled the version, cleared registry. Restarted the PC. Installed a older version of chromium, and get the same results. Unable to log into gmail account.
,
Jun 13 2018
,
Jun 13 2018
Thanks for filing the issue! As the issue looks very similar to that of https://bugs.chromium.org/p/chromium/issues/detail?id=844250 hence duplicating into it, Please feel free to undupe if both aren't similar. Removing Needs-bisect label.
,
Jun 13 2018
vamshi.kommuri@chromium.org I can't open this issue https://bugs.chromium.org/p/chromium/issues/detail?id=844250 (don't have permission) so don't know about duplicate.
,
Jun 13 2018
@romanxxx7: I think now you don't need any permission to open the bug mentioned in C#5/6 as it is marked as Public now. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by romanx...@gmail.com
, Jun 12 2018329 KB
329 KB View Download