Hi, I newly installed this "chromium.woolyss.com" RobRich-avx2 version of Chromium. When first start, I choose "sign in" option and input my google account and password, then the 2-step verification work well, Google says my account is logging in, and I choose "Yes, it's me" when comfirming.
But with all these seem good, after "sign in", the browser can't sign in and stop at a all blank state, following is the screenshot:
Waiting a long time doesn't help.
If I close it and run the Chromium into normal state, there is "sign in to Chromium" button:
After I sign in with google account with this button and input my google account and password, it's the same "all these seem good", but browser can't sign in and can't setup sync:
Instead, it jumps to www.google.com and sign my account in to the google website, just as top right corner shows.
How to solve it? Is it a bug?
From September last year (Sep. 2025), this problem already appears, I forget the version number. When I post this issue now, I use Chromium v149.0.7785.0-r1613160-win64-avx2 (About Chromium shows: Version 149.0.7785.0 (Official Build) (64-bit), and in this version, this problem still exists.
Hi, I newly installed this "chromium.woolyss.com"
RobRich-avx2version of Chromium. When first start, I choose "sign in" option and input my google account and password, then the 2-step verification work well, Google says my account is logging in, and I choose "Yes, it's me" when comfirming.But with all these seem good, after "sign in", the browser can't sign in and stop at a all blank state, following is the screenshot:
Waiting a long time doesn't help.
If I close it and run the Chromium into normal state, there is "sign in to Chromium" button:
After I sign in with google account with this button and input my google account and password, it's the same "all these seem good", but browser can't sign in and can't setup sync:
Instead, it jumps to www.google.com and sign my account in to the google website, just as top right corner shows.
How to solve it? Is it a bug?
From September last year (Sep. 2025), this problem already appears, I forget the version number. When I post this issue now, I use Chromium
v149.0.7785.0-r1613160-win64-avx2(About Chromiumshows:Version 149.0.7785.0 (Official Build) (64-bit), and in this version, this problem still exists.