It seems that there is a regression, see ansible logs attached.
This is run in a post install chroot.
=> Installing the chromium snap
==> Checking connectivity with the snap store
===> Unable to contact the store, trying every minute for the next 30
minutes
===> Still unable to contact the store, trying for another 20 minutes
===> Still unable to contact the store, trying for another 10 minutes
===> Still unable to contact the store, aborting
dpkg: error processing archive
/var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb
(--unpack):
new chromium-browser package pre-installation script subprocess returned
error exit status 1
** Attachment added: "ansible.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+attachment/5494610/+files/ansible.log
--
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 Released
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
