That regression is being tracked and investigated in a separate bug
report (bug #1927071).
--
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
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
This bug was fixed in the package chromium-browser -
83.0.4103.97-0ubuntu0.20.04.1
---
chromium-browser (83.0.4103.97-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release: 83.0.4103.97
* Do not attempt to install the snap on systems where snapd isn't running
Right, my testing was incomplete indeed.
I enabled focal-proposed for universe in a fully up-to-date focal VM (amd64),
and verified that issuing "apt install chromium-browser" installed version
83.0.4103.97-0ubuntu0.20.04.1, and that the installation completed successfully
and installed the
Please also verify "that installing the package on systems that are
capable of running snapd (e.g. virtual machines or bare metal) still
works as expected" per the Regression Potential section of the bug
description.
** Changed in: chromium-browser (Ubuntu Focal)
Status: Fix Committed =>
I enabled focal-proposed for universe in a fully up-to-date focal
chroot, and verified that issuing "apt install chromium-browser"
installed version 83.0.4103.97-0ubuntu0.20.04.1, and that the
installation completed in a reasonable amount of time. Relevant excerpt
of the output:
Preparing to
If the snap installation failed at deb installation/upgrade, it is left
as an exercise to the user to manually install (as suggested by the help
text displayed by /usr/bin/chromium-browser). So this is the intended
behaviour.
--
You received this bug notification because you are a member of
Oups
```
Command '/usr/bin/chromium-browser' requires the chromium snap to be installed.
Please install it with:
snap install chromium
```
when should it trigger snap installation ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Just tried with -proposed repo, installation of chromium-browser package
doesn't hang in a chroot anymore.
After first reboot the package is installed in version:
83.0.4103.97-0ubuntu0.20.04.1
Please change tag from verification-needed-focal to verification-done-
focal.
--
You received this
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
** Description changed:
+ [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
** Also affects: chromium-browser (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: chromium-browser (Ubuntu Focal)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in:
This bug was fixed in the package chromium-browser -
83.0.4103.97-0ubuntu1
---
chromium-browser (83.0.4103.97-0ubuntu1) groovy; urgency=medium
* New upstream release: 83.0.4103.97
* Do not attempt to install the snap on systems where snapd isn't running
(including chroots and
Fixed with https://bazaar.launchpad.net/~chromium-team/chromium-browser
/groovy-stable/revision/1540.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Branch linked: lp:~chromium-team/chromium-browser/groovy-stable
--
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
That code is pretty new in the lxd deb2snap, it was added with
https://github.com/lxc/lxd-pkg-ubuntu/pull/42. I'll test and replicate
in the chromium deb2snap.
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Changed in: chromium-browser (Ubuntu)
Assignee:
In lxd deb2snap we have this:
# Check store connectivity
echo "==> Checking connectivity with the snap store"
COUNT=0
SKIP=false
while :; do
if skip_unusable_snapd; then
echo "===> System doesn't have a working snapd and LXD was
We had a lot of conversations on IRC about this.
tl;dr overall, the UX is bad and confusing and must be improved.
** Description changed:
Since snapd integration, chromium-browser package fails to install in a post
kickstart chroot.
As APT obfuscate snap installation, I worry about auto
** Summary changed:
- install chromium-browser in a chroot fails
+ Fresh install of chromium-browser during installer-like process, in a chroot
fails (when preparing machines prior to first boot)
--
You received this bug notification because you are a member of Desktop
Packages, which is
19 matches
Mail list logo
