On Mon, Apr 06, 2020 at 04:11:03PM -0000, Olivier Tilloy wrote: > > Why is the chromium snap using per-version state directories? I think > > fixing that would be much more important in terms of usability.
> That's because the file format for the profile directory can change with > new versions, and is not guaranteed to be backward-compatible. Reverting > to an old revision shouldn't leave users with an unusable profile > directory. As a user, that is far less important to me than the fact that *every single time* there is a snap refresh, Google Meet stops working, I have to restart Chromium, it reports that Chromium did not shut down cleanly, and part of my session state has been lost with no chance to preserve it. I think the state should all be moved to the common dir until you have a way to handle the rollback case without making the *upgrade* case terrible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616650 Title: snap refresh while command is running may cause issues To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
