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 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.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: rls-gg-incoming
--
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:
Confirmed
Bug 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
