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.

Sign up for GitHub

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

Jump to bottom

Under Chromium snap, data is not saved between a Chromium refresh and a restart. #215

Open
cxw42 opened this issue Jun 8, 2020 · 0 comments
Open

Under Chromium snap, data is not saved between a Chromium refresh and a restart. #215

cxw42 opened this issue Jun 8, 2020 · 0 comments
Labels
blocked-by-upstream A bug in software other than TabFern that needs to be fixed there bug confirmed Bugs that have been reproduced by one of the developers target-chrome Chrome-specific issues

Comments

@cxw42
Copy link
Owner

cxw42 commented Jun 8, 2020

Summary: Whenever Chromium tells you "restart to apply updates", make a backup in TabFern, then restart right away!

This is caused by upstream https://bugs.launchpad.net/snapd/+bug/1616650 . When the Chromium snap refreshes, and you get a "restart to apply updates" notification, saving of data is silently disabled until you restart Chromium. There is not much that TabFern can do about this, unfortunately.

#214 would help with the workaround.
@cxw42 cxw42 added bug target-chrome Chrome-specific issues blocked-by-upstream A bug in software other than TabFern that needs to be fixed there confirmed Bugs that have been reproduced by one of the developers labels Jun 8, 2020
@cxw42 cxw42 pinned this issue Jun 8, 2020
@cxw42 cxw42 mentioned this issue Aug 6, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked-by-upstream A bug in software other than TabFern that needs to be fixed there bug confirmed Bugs that have been reproduced by one of the developers target-chrome Chrome-specific issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cxw42