Public bug reported:
When the chromium snap is being automatically refreshed to a newer
revision while the app is running, undefined behaviour might happen, as
well as data loss (because the profile folder is versioned). This issue
is regularly being reported (see e.g. the duplicates of bug #1616650).
Jamie has an interesting suggestion to mitigate this situation, until
refresh app awareness becomes default:
« […] it would be possible for you to run something in the
background that could occasionally see if the current symlink changed,
and then alert to restart
whenever refresh app awareness lands, it could be converted to see
if something is pending, if so, prompt/alert to stop to have updates
applied, or something
simple idea is to nohup a script in a wrapper before invoking
chromium proper
iirc, firefox used to have UX built into it letting the user know it
needed to be restarted, so there is some precedent for this sort of
thing »
** Affects: chromium-browser (Ubuntu)
Importance: Wishlist
Assignee: Olivier Tilloy (osomon)
Status: Triaged
** Tags: snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864901
Title:
[snap] suggestion: alert users when the snap has been refreshed while
running
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
