chromium-browser user data gets copied to per-snap-revision directory while chromium is running, leads to data loss and "chromium did not shut down correctly"
Bug #1852809 reported by
Steve Langasek
This bug report is a duplicate of:
Bug #1616650: snap refresh while command is running may cause issues.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I noticed that after the switch to a snap in eoan, in a case where I knew I had manually shut down chromium cleanly, I got an error on restart saying that it had not been shut down cleanly. Digging around on the filesystem led me to realize that a snap refresh had happened and the profile had been copied over while still in use.
The unclean shutdown message is annoying but not critical. More important is that this means any data written to the profile (cookies, passwords, etc) by the still-running instance of the old chromium, after the snap refresh, are not retained.
| tags: | added: snap |
Revision history for this message
| Olivier Tilloy (osomon) wrote | #1 |
To post a comment you must log in.
This is bug #1616650, and it is being addressed by https:/
snap set core experimental.
This will prevent chromium (and any other snap) from updating while it's running.
I have been testing this for over a month, and it seems to be working well.