Skip to content
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

Closed
graphixillusion opened this issue Feb 19, 2024 · 11 comments
Closed

Session data is not saved in v122.0.6261.56 #135

graphixillusion opened this issue Feb 19, 2024 · 11 comments

Comments

@graphixillusion
Copy link

graphixillusion commented Feb 19, 2024

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.

@dfa56
Copy link

dfa56 commented Feb 20, 2024

Hi, chrome://settings/content/siteData

@graphixillusion
Copy link
Author

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.

@macchrome
Copy link
Owner

OK, well spotted.

@E021ntox
Copy link

The flag is --disable-encryption. With 122 i need to use --disable-encryption-win and with it it does work as expected.

How did you find this new flag? No information found on Google...

@ltguillaume
Copy link

ltguillaume commented Feb 21, 2024

The flag is --disable-encryption. With 122 i need to use --disable-encryption-win and with it it does work as expected.

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: --disable-encryption still works, while with --disable-encryption-win all (session) data and settings are lost.

@E021ntox
Copy link

E021ntox commented Feb 21, 2024

@ltguillaume --disable-encryption-win works fine in my case. --disable-encryption is dead.

See this: https://github.com/portapps/portapps.github.io/blob/dev/src/_includes/app/infos/ungoogled-chromium.md

@graphixillusion
Copy link
Author

@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

@ltguillaume
Copy link

ltguillaume commented Apr 11, 2024

The existence of a --disable-encryption-win switch seems to have been debunked in ungoogled-software/ungoogled-chromium#591 (comment) unless it is specific to @macchrome's build:

Well, passing --disable-encryption-win to chromium is the same as passing nothing. It's just an invalid argument. disable-encryption-win doesn't even exist in either UG or winchrome. image

@graphixillusion
Copy link
Author

@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.

@ltguillaume
Copy link

I just saw this patch that is related to the same issue: Alex313031/thorium@1ac0e00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@ltguillaume @macchrome @graphixillusion @E021ntox @dfa56 and others