[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 (including chroots and WSL) (LP: #1882232) -- Olivier Tilloy Mon, 08 Jun 2020 22:48:58 +0200 ** Changed in: chromium-browser (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 chromium snap indeed. For good measure I verified that running "chromium-browser" did launch the snap. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Changed in: chromium-browser (Ubuntu Focal) Status: Incomplete => Fix Committed -- 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 => Incomplete ** Tags removed: verification-done-focal ** Tags added: 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: Incomplete 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 unpack .../chromium-browser_83.0.4103.97-0ubuntu0.20.04.1_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> System doesn't have a working snapd, skipping Unpacking chromium-browser (83.0.4103.97-0ubuntu0.20.04.1) ... Setting up chromium-browser (83.0.4103.97-0ubuntu0.20.04.1) ... ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Tags removed: 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: 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
** 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 (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. -- 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: In Progress 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
** 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: chromium-browser (Ubuntu Focal) Status: New => In Progress -- 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: In Progress 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 WSL) (LP: #1882232) -- Olivier Tilloy Mon, 08 Jun 2020 17:49:24 +0200 ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 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 Committed 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
** 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 installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: Fix Committed 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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: (unassigned) => Olivier Tilloy (osomon) -- 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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 never used, skipping" SKIP=true break fi similar does not exist in chromium-browser, but must. -- 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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
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
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
** 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 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: Incomplete 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. 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
