On Mon, Apr 06, 2020 at 12:43:20PM -0000, Olivier Tilloy wrote:
> No, there is a much better (albeit not perfect) solution: enable
> experimental.refresh-app-awareness, so automatic refreshes will be held
> for a maximum of 7 days. So closing chromium (or any other affected
> snap) and applying updates is needed only once a week.
That's really not a satisfactory solution. I don't restart my browser
weekly unless I'm forced to, it doesn't matter if this happens one day or
seven days after the new snap has become available on the channel.
Why is the chromium snap using per-version state directories? I think
fixing that would be much more important in terms of usability.
On Mon, Apr 06, 2020 at 12:43:20PM -0000, Olivier Tilloy wrote: refresh- app-awareness, so automatic refreshes will be held
> No, there is a much better (albeit not perfect) solution: enable
> experimental.
> for a maximum of 7 days. So closing chromium (or any other affected
> snap) and applying updates is needed only once a week.
That's really not a satisfactory solution. I don't restart my browser
weekly unless I'm forced to, it doesn't matter if this happens one day or
seven days after the new snap has become available on the channel.
Why is the chromium snap using per-version state directories? I think
fixing that would be much more important in terms of usability.