tarantula!root# snap refresh
core18 20200427 from Canonical✓ refreshed

tarantula!root# snap refresh
All snaps up to date.

tarantula!root# snap list | grep chromium
chromium           81.0.4044.122    1119   latest/stable  canonical*    -

tarantula!root# snap info --abs-time chromium
name:      chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more 
stable way for all
  Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:      XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking:     latest/stable
refresh-date: 2020-04-25T11:23:52+03:00
channels:
  latest/stable:    81.0.4044.129 2020-04-29T17:25:51Z (1135) 161MB -
  latest/candidate: 81.0.4044.129 2020-04-28T18:04:52Z (1135) 161MB -
  latest/beta:      83.0.4103.23  2020-04-25T02:07:58Z (1125) 163MB -
  latest/edge:      84.0.4128.3   2020-04-29T05:50:21Z (1136) 164MB -
installed:          81.0.4044.122                      (1119) 161MB -

-- 
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/1864901

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  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 »

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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

Reply via email to