Hello Jo, or anyone else affected,

Accepted chromium-browser into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/chromium-
browser/83.0.4103.97-0ubuntu0.20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: chromium-browser (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Fresh install of chromium-browser during installer-like process, in a
  chroot fails (when preparing machines prior to first boot)

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Users trying to install chromium-browser with apt in a chroot will see the 
preinst script hang for 30min, and eventually fail.
  This use case is important as chroots are used by sysadmins to prepare 
installers.

  [Test Case]

  Create a focal chroot (for example using "pcreate -a amd64 -d focal 
focal-amd64"), enter the chroot and run "apt install chromium-browser".
  Expected outcome: the installation succeeds, even though the chromium snap is 
not being installed because snapd cannot run in the chroot.
  Incorrect (current) outcome: the installation hangs during 30 minutes while 
trying to contact the snap store, and eventually fails.

  [Regression Potential]

  As this change modifies the chromium-browser preinstallation script,
  it should be verified that installing the package on systems that are
  capable of running snapd (e.g. virtual machines or bare metal) still
  works as expected.

  [Original Description]

  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

  When a user is running the installer, and instructs to install
  chromium-browser with apt in the /target chroot the experience is
  extremely bad.

  There are timeouts, there is critical debconf prompt, and no
  explanation as to what is happening.

  This is not an upgrade, and no conversion from deb2snap is needed.

  It is in a chroot, because this is how installers work.

  It feels like as if on fresh install of chromium-browser it should try
  "snap install --now-or-schedule-for-later chromium-browser" such that
  if snapd is running and available install it now, otherwise record a
  task for snapd to execute if and when it comes up (on first boot). Or
  like for example, it should call snap prepare-image --classic instead.

  Overall, imho on new installations of the package, if there is no
  snapd running, it should be skipped without asking any questions or
  popping up any dialogues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to