New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session data is not saved in v122.0.6261.56 #135
Comments
Hi, chrome://settings/content/siteData |
As suggested: chrome://settings/content/siteData ungoogled-software/ungoogled-chromium#2681 https://github.com/ungoogled-software/ungoogled-chromium/pulls?q=cookie https://github.com/ungoogled-software/ungoogled-chromium/issues?q=cookie |
I think i have understood what's going on: the problem seems to be a wrong flag passed to the executables which doesn't work anymore with 122. The flag is --disable-encryption. With 122 i need to use --disable-encryption-win and with it it does work as expected. |
OK, well spotted. |
How did you find this new flag? No information found on Google... |
@graphixillusion Plus, it's simply not true as far as I can tell: |
@ltguillaume |
@ltguillaume i don't know what's going on but i have the same results as @E021ntox: --disable-encryption-win works fine in 122. --disable-encryption doesn't work anymore. This is just happened in the last 122 build: 121 works fine with the --disable-encryption flag |
The existence of a
|
@ltguillaume you are right, after your post i did some tests and actually --disable-encryption-win is equal to passing nothing but --disable-encryption still didn't work on my portable installation. So i tried again fresh (deleting the profile folders) and now it seems to works again. I still don't understand the reason and/or why this happens. |
I just saw this patch that is related to the same issue: Alex313031/thorium@1ac0e00 |
Hi there. As the title says, with the last version (122.0.6261.56) the session data is not saved when you close and reopen the program. So if you login into something, close and reopen chromium, the session cookie is erased so you need to login again. ungoogled-chromium-122.0.6261.56-2 is affected too by this problem. ungoogled-chromium-121.0.6167.185-1 doesn't have this problem and works good.
The text was updated successfully, but these errors were encountered: