Unable to login to vk.com

Flashwalker commented 1 year ago

OS/Platform

Debian, Ubuntu, and derivatives

Installed

Flatpak

Version

105.0.5195.125

Have you tested that this is not an upstream issue or an issue with your configuration?

[X] I have tried reproducing this issue in Chrome and it could not be reproduced there
[X] I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
[ ] I have tried reproducing this issue in ungoogled-chromium with a new and empty profile and it could not be reproduced there

Description

Unable to login on vk.com

How to Reproduce?

use clean profile
allow all cookies in settings
go to vk.com
try to login
see error:

Actual behaviour

got login error

Expected behaviour

login success

Relevant log output

No response

Additional context

Tried on fresh new profile ungoogled-chromium-flatpak --user-data-dir=/tmp/tmp-data-dir, got the same issue;
Login to vk.com works on ungoogled-chromium v.98 .deb package;
Login to vk.com works on vanila chromium appimage;

networkException commented 1 year ago

Are there any error messages in the javascript console?

Flashwalker commented 1 year ago

Are there any error messages in the javascript console?

There were no errors in the console or in the network panel.

I found the root of the issue.
My user-data-dirs were somehow mixed up after upgrading from deb version 98 to flatpak 105.
After updating, I copied the contents of the old user-data-dir folder into the new place for flatpak.
And it looks like the flatpak version used to eat from both sources, the old 98 folder and the new one for the 105. Which was causing the login problem. Now I just deleted the old folder and login works again.

Flashwalker commented 1 year ago

It looks like the --user-data-dir option was passed twice, for the old and new folders.
The latter option gave me a clean profile, as I could tell from the vanila look and feel. But that's not what happened under the hood actually.
imho the last one should have override the first one, but it seemed to work somehow both of them

Flashwalker commented 1 year ago

I found that the option: --disable-web-security causes this issue

ungoogled-software / ungoogled-chromium