search

RobRich999 / Chromium_Clang

Chromium browser compiled with the Clang/LLVM compiler.
172 stars 12 forks source link

gmail #4

Closed uBlock-user closed 6 years ago

uBlock-user commented 6 years ago

@RobRich999

Can't login to gmail or my google account because of NoSync via - https://mail.google.com/mail/

Why ? This didn't happen before, it's now as if I can't access any Google services with my account.

This is what happens - https://i.gyazo.com/b700d988163c5f7c62a513b24b2d2b0e.png

RobRich999 commented 6 years ago

It is a known problem in Chromium. Has happened before. The workaround is to disable the account consistency flag setting.

chrome://flags/#account-consistency

I will see about digging up the old Chromium bug report and updating it. Thanks!

uBlock-user commented 6 years ago

Thanks a lot, I was about to remove your builds, because this is a deal breaker if I can't access gmail and other such services.

RobRich999 commented 6 years ago

Took a look. The project is finally rolling out DICE, an updated authentication process for Google services. You might eventually have to tweak the flag to "prepare migration...." or "fix auth errors" in the near future.

uBlock-user commented 6 years ago

Yeah I tweaked and experimented a bit and it works. Would you mind doing SYNC builds ?

RobRich999 commented 6 years ago

I do not use Google API keys, thus the reason for no sync support.

uBlock-user commented 6 years ago

What I meant is would you do it for the users like me and others, even though you don't use them.

RobRich999 commented 6 years ago

Probably not at this time, but I will put on the consideration list.

For the most part, ya'll get the same builds I personally use. ;)

uBlock-user commented 6 years ago

Thanks, I hope you consider it and let me know when you do.

RobRich999 commented 6 years ago

Quick FYI. My latest Windows builds (and soon Linux) now include a modification to force "dice_fix_auth_errors," which resolves the Google login issue (for now) without having to set a custom flag.

uBlock-user commented 6 years ago

just an FYI - your latest 64 bit build has chrome://history/ page broken, browsing history doesn't appear when opened - https://i.gyazo.com/3c9bb78f43d7b8cf062afdaeafb49f5f.png

RobRich999 commented 6 years ago

I have a new build out. Appears resolved, so it was likely a revision issue.

uBlock-user commented 6 years ago

No change on my end, nothing appears.

Last working build - 68.0.3440.0-r561732-win64 all builds after that have chrome://history tab broken.

RobRich999 commented 6 years ago

Working here. Check extensions and any related flags.

uBlock-user commented 6 years ago

I only have three extensions, disabled all of them and no change.

About flags, I have - Smooth Scrolling, QUIC, TLS 1.3, Autoplay Policy, Block Tab-unders. None of them have ever did this before.

I'm on Windows 10 Pro x64 1803 build FYI

uBlock-user commented 6 years ago

I disabled all of those flags and rebooted Chromium, still the same. This is something screwed up with Chromium itself, because 68.0.3440.0-r561732-win64 works fine with the same settings.

RobRich999 commented 6 years ago

I can not replicate the issue here. Have you checked https://www.crbug.com for a related bug report?

uBlock-user commented 6 years ago

I tried a RAW build from https://download-chromium.appspot.com/ and it happens there too, so definitely something's screwing it up, probably a issue with the Windows 10 April update.

Have you checked https://www.crbug.com for a related bug report?

Yes, I did and nobody has filed any bug report, so I filed one myself -https://bugs.chromium.org/p/chromium/issues/detail?id=850001

The devs haven't seen it yet and I don't know if they ever will as new bug reports keep getting filed up and this one keeps getting pushed down, not sure what to expect at this juncture.

uBlock-user commented 6 years ago

Okay, I finally managed to fix this issue. Here's what happened -- Back when I first reported about the broken history page the issue did exist, but like as you said in the subsequent post, it was indeed a revision issue and was fixed in the subsequent build, but any subsequent builds wouldn't work for me, because that bugged build corrupted my browsing data.

So no matter which build I ran, it always ended with the same result, so I decided to delete all my browsing data. Lo! and Behold!, it's working normally and history's showing up now, so bad builds CAN corrupt your browsing data/history which will cause the issue to persist further, fortunately deletion took care of that for good.