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

Site data keep getting deleted after an update #2919

Open
3 tasks
mndctrlwpn opened this issue Jun 17, 2024 · 6 comments
Open
3 tasks

Site data keep getting deleted after an update #2919

mndctrlwpn opened this issue Jun 17, 2024 · 6 comments
Labels
bug need info Need feedback to proceed

Comments

@mndctrlwpn
Copy link

mndctrlwpn commented Jun 17, 2024

OS/Platform

Debian, Ubuntu, and derivatives

Installed

Flatpak

Version

all

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

  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • 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 using --user-data-dir command line argument and it could not be reproduced there

Description

After running a flatpak update, ungoogled-chromium deletes all site data forcing you to log into everything again

How to Reproduce?

  1. Log into website on ungoogled chromium and check the box that says "keep me logged in"
  2. Close window
  3. Run "flatpak update" command in terminal
  4. Open ungoogled chromium, no longer logged in

Actual behaviour

Despite my settings set to "keep all cookies", every update seems to throw my cookies and site data out the window. This is frustrating, especially since I'm usually logged into many sites and cannot stand logging in all over again to all of them. Behaviour seems random; sometimes it happens and sometimes it doesn't, but the issue has persisted for months of updates now.

Expected behaviour

I keep my cookies after an update.

Relevant log output

No response

Additional context

No response

@mndctrlwpn mndctrlwpn added the bug label Jun 17, 2024
@touba-denrael
Copy link

not perfectly sure if it is relevant because of the random behaviour you just described, but you might want to check if the chrome://flags/#clear-data-on-exit flag is on its default or disabled setting.

@mndctrlwpn
Copy link
Author

It was indeed set to default, now disabled. Let's see if this helps. Might take some time to be sure.

That's strange, though. I've closed my browser many many times, is that not the same as exiting?

@touba-denrael
Copy link

touba-denrael commented Jun 18, 2024

the chrome://flags/#clear-data-on-exit default setting [usually] should be perfectly sufficient [my failure in wording], the important thing is, it should not be set to enabled if one wants to keep the data.

you might also want to back up somewhere else on your drive [or just temporarily rename] your .config/chromium directory, then try to run the program through the new empty profile created, testing if the behaviour persists after program closings [program exits].

you might also use the command line argument --user-data-dir to define your new temporary user directory for testing the ways the program closes [exits].

with these settings #2873 (comment) the behaviour of the program should be as intended [now just waiting for people with more knowledge about running, updating, programs through flatpak than me].

@PF4Public
Copy link
Contributor

@mndctrlwpn So, does it work properly now?

@PF4Public PF4Public added the need info Need feedback to proceed label Jul 4, 2024
@mndctrlwpn
Copy link
Author

@mndctrlwpn So, does it work properly now?

Sadly no, meant to report on this again earlier. Behaviour is unchanged :(

@PF4Public
Copy link
Contributor

@rany2 Sorry for pinging you, could we have yet another issue with flatpak?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug need info Need feedback to proceed
Projects
None yet
Development

No branches or pull requests

3 participants