Public bug reported:
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.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: snap
** Tags added: snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1852809
Title:
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"
Status in chromium-browser package in Ubuntu:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852809/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
