Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[andresgenovez]

[Impact]
Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway.

We have two changes that help address this:

* The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here.

* The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything).

[Test case]
We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors.

TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case.

[Regression potential]
It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely.

Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern.

[Groovy SRU]
The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates.

We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows.

[Original bug report]
Test Case
1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers
2. Proceed with installation

The following error message is displayed in /var/log/syslog
/plugininstall.py: Verifying downloads ...
/plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found."
/plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found."
/plugininstall.py: Downloads verified successfully
ubiquity: Error in function: install
/plugininstall.py: Exception during installation:
/plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
/plugininstall.py:

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.9
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CasperVersion: 1.442
Date: Mon Apr 6 20:17:07 2020
InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 LANGUAGE=es_EC.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_EC.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Pierre Equoy (pieq)]

Facing a crash that looks similar.

In ubiquity install.trace file, I can see:

    apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)

Device: Dell Vostro 5590
Image: Focal 20.04 beta
Install: connected to the Internet (using an Ethernet cable)
Install options:
 - erase disk and install Ubuntu
 - use LVM partitioning
 - use encryption

I installed 20.04 a few weeks ago on the same device and didn't face this issue.

Also, I tried booting in "safe graphics mode" for the install but it didn't help.

[Pierre Equoy (pieq)]

Forgot to mention I'm using Ubuntu image, not Xubuntu.

[Pierre Equoy (pieq)]

One more info: my system has a nvidia card and has secure boot enabled.

[Pierre Equoy (pieq)]

If the exact same installation process is followed *without being connected to the Internet*, the installation can be completed successfully.

[Matthias Klose (doko)]

UbiquitySyslog reads:

Apr 7 01:14:40 xubuntu /plugininstall.py: Verifying downloads ...
Apr 7 01:14:41 xubuntu /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
Apr 7 01:14:41 xubuntu /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found."
Apr 7 01:14:41 xubuntu /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
Apr 7 01:14:47 xubuntu /plugininstall.py: Downloads verified successfully
Apr 7 01:14:48 xubuntu ubiquity: Error in function: install
Apr 7 01:14:48 xubuntu /plugininstall.py: Exception during installation:
Apr 7 01:14:48 xubuntu /plugininstall.py: apt_pkg.Error: E:No se pudo configurar «libc6:i386», E:No se pudo realizar la configuración inmediata de «libgcc-s1:i386». Consulte la página de manual con «man 5 apt.conf» bajo «APT::Immediate-Configure» para más información. (2)
Apr 7 01:14:48 xubuntu /plugininstall.py:

apparently some downloads failed, and ubiquity seems to ignore that errror, and tries to continue. how is libc6:i386 involved with that? out of sync mirrors?

[Dimitri John Ledkov (xnox)]

So, we have by-hand calculated list of packages that are included from the i386 repo onto the amd64.

[Dimitri John Ledkov (xnox)]

And we need to update it.

[erio (eri0)]

I have a i5 4th generation and a NVIDIA GTX 970, I hit this bug trying to install 20.04 from the Beta build.

[Dimitri John Ledkov (xnox)]

Proposed fixed https://code.launchpad.net/~xnox/debian-cd/update-i386-pool/+merge/382110

[Rajat Pandita (rajat-pandita)]

This is a new observation, This did not happen before, The install is however successful, and I can login fine. Hope this helps

[Doug Brunelle (dougbrunelle)]

I had this installer crash just now. (Apr 19, 2020)

* Computer: MSI GT72 6QD laptop, 16MB RAM, Nvidia GTX970M video. Installing to a 1TB SATA SSD drive.
* Used the installation option to use Internet connection to install third-party software (wired Ethernet connection to router)
* Already have Ubuntu Studio 19.10 and Windows 10 on a separate PCI-E SSD.

Note: I got thru the partitioning section, login name setup, and the installer progress showed being about 3/4 done (installing system message) when the crash occurred.

[Steve Langasek (vorlon)]

Doug, this was fixed by including the missing i386 packages in a newer image. What image did you see this issue with? You need to be using the latest daily image to get the fix.

[Bill (franksmcb) (franksmcb)]

This is occurring on the the Ubuntu MATE 20.04 Focal Final release. 20200419

Occurs during the installation and the installer crashes.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1871268

[Steve Langasek (vorlon)]

I have verified that the libgcc-s1:i386 binary package is included in the package pool including on the Ubuntu Mate 20200419 daily image. Can someone who is experiencing this issue please attach their full syslog from the live environment, so that we can reconfirm what's going on?

[Yousuf 'Jay' Philips (philipz85)]

Installation went fine for me with my GT 640M LE prime setup with the 20200420 daily image.

[Bill (franksmcb) (franksmcb)]

I have installed using the latest 20200420 image of Ubuntu MATE and this issue is not occurring, installation completes successfully.

[Monica R Ayhens-Madon (madhens)]

Have GTX 1660 and did an install of latest 20200420 and did not experience error as reported, but have attached tarball of /var/log/ from live environment, if it can be useful.

[Sebastian Witthus (kn4llfrosch)]

RTX2070, still seeing this with the image I downloaded 1 hour ago. Ethernet was connected and I chose to download packages during installation.

[thrantir (thrantir)]

I got the same error with an image downloaded on saturday, with the image downloaded 20 minutes ago the problem didn't happen

[Perke Valo (perkevalo)]

my computor crashed when I tried to make a 32 bit ghost drive ti wine..couldent boot at all so I did install a new one moohahahh

[Steve Langasek (vorlon)]

@kn4llfrosch please indicate which image you downloaded, not just when you downloaded it.

Also, without the log files that I previously requested, we are not going to be able to further debug any remaining failures which are not reproducible for the developers.

[Gustaf Lindström (gustaf-lindstroem)]

Got this while installing from a daily build of groovy-desktop-amd64 from 2020-06-02. System connected to the internet, updates while installing enabled, third-party installs enabled and I've got an NVIDIA card as well.

[Vadim Zeitlin (vz-ubuntu)]

Although this is marked as "Invalid" for 20.04, this problem has somehow started happening in GitHub Actions Ubuntu 20.04 virtual environment since today (2020-07-24), even though it worked correctly before. I don't know if attaching the entire build log is desirable, but as the result of running these commands

2020-07-24T22:46:28.8786226Z sudo dpkg --add-architecture i386
2020-07-24T22:46:28.8786352Z sudo apt-get update
2020-07-24T22:46:28.8786474Z sudo apt-get --assume-yes install \
2020-07-24T22:46:28.8786604Z automake bc bsdmainutils bzip2 curl cvs default-jre \
2020-07-24T22:46:28.8786724Z g++-mingw-w64-i686 g++-multilib git jing libarchive-tools \
2020-07-24T22:46:28.8786866Z libtool libxml2-utils libxslt1-dev make patch pkg-config rsync \
2020-07-24T22:46:28.8787006Z shellcheck sudo trang unzip wine32 wget xsltproc

I get, after many snipped lines, the following error:

2020-07-24T22:50:38.3418072Z Processing triggers for libc-bin (2.31-0ubuntu9) ...
2020-07-24T22:50:38.4346359Z Processing triggers for libgdk-pixbuf2.0-0:i386 (2.40.0+dfsg-3) ...
2020-07-24T22:50:38.4858494Z Processing triggers for wine (5.0-3ubuntu1) ...
2020-07-24T22:50:40.0498037Z E: Could not configure 'libc6:i386'.
2020-07-24T22:50:40.0499968Z E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
2020-07-24T22:50:40.0526698Z ##[error]Process completed with exit code 100.

and there don't seem to be any other errors in the output until these lines, so I have no idea why does this happen.

FWIW the same step of this workflow succeeds when run in Ubuntu 18.04-based GitHub virtual environment, but it doesn't have sufficiently up-to-date packages for building this software, so I can't use it and would really appreciate any workaround for this problem under 20.04.

[Vadim Zeitlin (vz-ubuntu)]

P.S. I've just finally found a workaround myself: doing "apt install libgcc-s1:i386" first, before installing anything else (but after "apt update"), allows the installation to succeed.

[Jackson Doak (noskcaj)]

A crash has redirected me to this bug using today's xubuntu 20.10 image. Attached is /var/log. This is on a Thinkpad T530 with nvidia graphics

[Guillermo Legarda Herranz (glegarda)]

I just got this error while attempting to install Ubuntu 20.04.1 LTS, which I downloaded this afternoon. I managed to get through the partitioning and username setting parts, but it crashed after that and I was redirected to this page.
I am using a ThinkPad P14s with NVIDIA graphics, I enabled update downloading during installation and third-party software installation. Any help would be appreciated.

[Randy E. Brinson (lifecoachrandy)]

Same error occurs with Kubuntu 20.04 & 20.04.01 and Xubuntu 20.04.01 -- this error occurs at 90-91% of the way through the install process. Suspect it's related to my video card: ASUS NVIDIA STRIX-GTX1050TI-04G-GAMING graphics card. This card worked perfectly up until last week with 20.04 Xubuntu and Kubuntu. All 64-bit. And it still works fine with Mint20. Guess I need to get a cheaper, crappier video card if I want to use *buntu going forward. {sigh}

[Trevin Corkery (trevinlc1997)]

This happened to me last night while trying to install Ubuntu on my desktop. It crashed and redirected me here.

One feature that I enabled was ZFS.

Desktop Specs:
Ryzen 3700x
GTX 1080ti
GSkillz Trident Z 8GB DDR4 3200mhz x2
Samsung 970 PRO
x370 Taichi

[Tianon Gravi (tianon)]

I'm running into this building a Docker image that's "FROM ubuntu:20.04" and just trying to install libc6:i386. Here's the simplest reproducer I've come up with:

```
$ docker pull ubuntu:20.04
20.04: Pulling from library/ubuntu
Digest: sha256:cbcf86d7781dbb3a6aa2bcea25403f6b0b443e20b9959165cf52d2cc9608e4b9
Status: Image is up to date for ubuntu:20.04
docker.io/library/ubuntu:20.04

$ docker run --rm ubuntu:20.04 sh -c 'dpkg --add-architecture i386 && apt-get update -qq && apt-get install -y libc6:i386'
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  gcc-10-base:i386 libc6 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386
  libunistring2:i386
Suggested packages:
  glibc-doc locales glibc-doc:i386 locales:i386
The following NEW packages will be installed:
  gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386
  libunistring2:i386
The following packages will be upgraded:
  libc6
1 upgraded, 6 newly installed, 0 to remove and 1 not upgraded.
Need to get 5871 kB of archives.
After this operation, 15.2 MB of additional disk space will be used.
...
Processing triggers for libc-bin (2.31-0ubuntu9) ...
E: Could not configure 'libc6:i386'.
E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
```

Looking at my GitHub Actions logs, it was working fine two days ago (Sep 21) and was broken starting yesterday (Sep 22), in case that helps narrow down which uploads might have caused the breakage.

[Brian Murray (brian-murray)]

On an Ubuntu Desktop system (which had not been updated for a while) I was able to recreate this by trying to install libc6:i386.

...
Processing triggers for libc-bin (2.31-0ubuntu9) ...
E: Could not configure 'libc6:i386'.
E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)

Interestingly no apport crash report was generated.

[Brian Murray (brian-murray)]

If libc-bin has been updated to 2.31-0ubuntu9.1 there is no such issue.

The following NEW packages will be installed:
  gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,159 kB of archives.
After this operation, 15.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://192.168.10.7/ubuntu focal/main i386 gcc-10-base i386 10-20200411-0ubuntu1 [19.0 kB]
Get:2 http://192.168.10.7/ubuntu focal/main i386 libgcc-s1 i386 10-20200411-0ubuntu1 [49.8 kB]
Get:3 http://192.168.10.7/ubuntu focal/main i386 libcrypt1 i386 1:4.4.10-10ubuntu4 [90.9 kB]
Get:4 http://192.168.10.7/ubuntu focal-updates/main i386 libc6 i386 2.31-0ubuntu9.1 [2,571 kB]
Get:5 http://192.168.10.7/ubuntu focal/main i386 libunistring2 i386 0.9.10-2 [377 kB]
Get:6 http://192.168.10.7/ubuntu focal/main i386 libidn2-0 i386 2.2.0-2 [51.4 kB]
Fetched 3,159 kB in 0s (27.7 MB/s)
Preconfiguring packages ...
Selecting previously unselected package gcc-10-base:i386.
(Reading database ... 259734 files and directories currently installed.)
Preparing to unpack .../0-gcc-10-base_10-20200411-0ubuntu1_i386.deb ...
Unpacking gcc-10-base:i386 (10-20200411-0ubuntu1) ...
Selecting previously unselected package libgcc-s1:i386.
Preparing to unpack .../1-libgcc-s1_10-20200411-0ubuntu1_i386.deb ...
Unpacking libgcc-s1:i386 (10-20200411-0ubuntu1) ...
Selecting previously unselected package libcrypt1:i386.
Preparing to unpack .../2-libcrypt1_1%3a4.4.10-10ubuntu4_i386.deb ...
Unpacking libcrypt1:i386 (1:4.4.10-10ubuntu4) ...
Selecting previously unselected package libc6:i386.
Preparing to unpack .../3-libc6_2.31-0ubuntu9.1_i386.deb ...
Unpacking libc6:i386 (2.31-0ubuntu9.1) ...
Selecting previously unselected package libunistring2:i386.
Preparing to unpack .../4-libunistring2_0.9.10-2_i386.deb ...
Unpacking libunistring2:i386 (0.9.10-2) ...
Selecting previously unselected package libidn2-0:i386.
Preparing to unpack .../5-libidn2-0_2.2.0-2_i386.deb ...
Unpacking libidn2-0:i386 (2.2.0-2) ...
Setting up gcc-10-base:i386 (10-20200411-0ubuntu1) ...
Setting up libcrypt1:i386 (1:4.4.10-10ubuntu4) ...
Setting up libgcc-s1:i386 (10-20200411-0ubuntu1) ...
Setting up libc6:i386 (2.31-0ubuntu9.1) ...
Setting up libunistring2:i386 (0.9.10-2) ...
Setting up libidn2-0:i386 (2.2.0-2) ...
Processing triggers for libc-bin (2.31-0ubuntu9.1) ...

[hong (tjdxph)]

When i install it i failed like this problem

[Adam (zyl0)]

Same happened to me. I suppose I will reattempt with the non-proprietary drivers and see if that will work out. Running an nVidia 1060 in an MSI laptop, SSD, 32GB ram, and was attempting to install the Voyager distro. The bug report directed me here, so here is my two cents. Sorry for the length I tried to cut it wherever it seemed to become relevant.

Sep 24 09:57:16 xubuntu ubiquity: Error in function: install
Sep 24 09:57:16 xubuntu /plugininstall.py: Exception during installation:
Sep 24 09:57:16 xubuntu /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
Sep 24 09:57:16 xubuntu /plugininstall.py:
Sep 24 09:57:16 xubuntu ubiquity:
Sep 24 09:57:16 xubuntu ubiquity: #015Get:66 http://us.archive.ubuntu.com/ubuntu focal/main i386 libxcb-randr0 i386 1.14-2 [18.0 kB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:67 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-5.4.0-48-generic amd64 5.4.0-48.52 [14.5 MB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:68 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-5.4.0-48-generic amd64 5.4.0-48.52 [8889 kB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:69 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-extra-5.4.0-48-generic amd64 5.4.0-48.52 [38.6 MB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:70 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-generic amd64 5.4.0.48.51 [1896 B]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:71 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-generic amd64 5.4.0.48.51 [2744 B]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:72 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.4.0-48 all 5.4.0-48.52 [11.0 MB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:73 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.4.0-48-generic amd64 5.4.0-48.52 [1255 kB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:74 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-generic amd64 5.4.0.48.51 [2612 B]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:75 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 linux-modules-nvidia-450-5.4.0-48-generic amd64 5.4.0-48.52 [11.5 MB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:76 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 nvidia-kernel-common-450 amd64 450.66-0ubuntu0.20.04.1 [18.6 kB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:77 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 linux-modules-nvidia-450-generic-hwe-20.04 amd64 5.4.0-48.52 [5476 B]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:78 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 mesa-vulkan-drivers i386 20.0.8-0ubuntu1~20.04.1 [3456 kB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:79 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 nvidia-compute-utils-450 amd64 450.66-0ubuntu0.20.04.1 [121 kB]
Sep 24 09:57:16 xubuntu ubiquity: #015Get:80 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted ...

[Stewart menday (stewartmenday)]

Just got this error, some further info,

GFX card - Nvidia Titan RTX
CPU - i9-10900X
MB - ASRock x299 Gaming K6
Installed OS - Win10 and Ubuntu 18.04, both installed to separate M.2 drives
Trying to install 20.04.01 to a 3rd M.2 drive

The install appears to be usable after the crash.
If you don't update drivers during install it will install without error.
If you don't update drivers during install, the installed system is unusable due to no/crazy screen output.

[Erwin (erwindeboer)]

Same error

Tried to install Ubuntu 20.04.1

Ryzen 3600

Nvidia 1660 super

[Zach Malter (zmalter99)]

Same error as well.

Ubuntu 20.04.1
Intel i7-8700k
RTX 2080
Z370 GAMING PRO CARBON

[Balint Reczey (rbalint)]

Easily reproducible on a system with libc6=2.31-0ubuntu9:

# apt install -o Debug::pkgPackageManager=True libc6:i386
...
Do you want to continue? [Y/n]
Beginning to order
Done ordering
  SmartUnPack libc6:amd64 (replace version 2.31-0ubuntu9 with 2.31-0ubuntu9.1) immediately
  Ignore not-installed version 2.31-0ubuntu9 of libc6:i386 for libc6:amd64 Breaks on libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > (!= 2.31-0ubuntu9.1)
    SmartUnPack libc6:i386 (install version 2.31-0ubuntu9.1)
    Ignore already dealt-with version 2.31-0ubuntu9 of libc6:amd64 for libc6:i386 Breaks on libc6:amd64 < 2.31-0ubuntu9 -> 2.31-0ubuntu9.1 @ii umU > (!= 2.31-0ubuntu9.1)
    SmartConfigure libc6:amd64 (2.31-0ubuntu9.1)
    Found ok dep libgcc-s1:amd64 < 10-20200411-0ubuntu1 @ii mK >
    Found ok dep libcrypt1:amd64 < 1:4.4.10-10ubuntu4 @ii mK >
      SmartConfigure libc6:i386 (2.31-0ubuntu9.1)
      Unpacking libgcc-s1:i386 to avoid loop libc6:i386 Depends on libgcc-s1:i386 < none -> 10-20200411-0ubuntu1 @un umN >
        SmartUnPack libgcc-s1:i386 (install version 10-20200411-0ubuntu1) immediately
          SmartConfigure libgcc-s1:i386 (10-20200411-0ubuntu1)
          Unpacking gcc-10-base:i386 to avoid loop libgcc-s1:i386 Depends on gcc-10-base:i386 < none -> 10-20200411-0ubuntu1 @un umN > (= 10-20200411-0ubuntu1)
            SmartUnPack gcc-10-base:i386 (install version 10-20200411-0ubuntu1) immediately
              SmartConfigure gcc-10-base:i386 (10-20200411-0ubuntu1)
          Configure already unpacked libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN >
            SmartConfigure libc6:i386 (2.31-0ubuntu9.1) (Only Correct Dependencies)
            Package libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > loops in SmartConfigure, but it isn't unpacked yet
            Package libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > loops in SmartConfigure, but it isn't unpacked yet
            Could not satisfy libc6:i386 Depends on libcrypt1:i386 < none -> 1:4.4.10-10ubuntu4 @un umN > (>= 1:4.4.10-10ubuntu4)
      Unpacking libcrypt1:i386 to avoid loop libc6:i386 Depends on libcrypt1:i386 < none -> 1:4.4.10-10ubuntu4 @un umN > (>= 1:4.4.10-10ubuntu4)
        SmartUnPack libcrypt1:i386 (install version 1:4.4.10-10ubuntu4) immediately
          SmartConfigure libcrypt1:i386 (1:4.4.10-10ubuntu4)
          Configure already unpacked libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN >
            SmartConfigure libc6:i386 (2.31-0ubuntu9.1) (Only Correct Dependencies)
            Configure already unpacked libgcc-s1:i386 < none -> 10-20200411-0ubuntu1 @un umN >
              SmartConfigure libgcc-s1:i386 (10-20200411-0ubuntu1)
              Configure already unpacked libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN >
                SmartConfigure libc6:i386 (2.31-0ubuntu9.1) (Only Correct Dependencies)
Skipping already done gcc-10-base:i386
...
Processing triggers for libc-bin (2.31-0ubuntu9) ...
E: Could not configure 'libc6:i386'.
E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
root@ff-glibc-i386:~# echo $?
100
root@ff-glibc-i386:~#

Apart from the error messages and the exit code 100 ...

[Rahul Shial (rahulshial)]

Dell L502X laptop / 256gb SSD / 16GB RAM
Windows 10 OS
Dual boot - Ubuntu 20.04.01 installation crashes with libc6:i386 configuration error.

At my wits end trying to make this work.

[Rahul Shial (rahulshial)]

Forgot to add:
Nvidia GT540 video card
installation of Ubuntu 20.04.01 via USB drive.

Trying to dual boot with windows 10.

[Balint Reczey (rbalint)]

At least Bionic's glibc is not affected.

[Manoel Cortes Mendez (baalinooo)]

Just happened to me too. I was redirected here. I was clean installing Ubuntu 20.04.1 LTS on a new Samsung SSD M.2.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Shashank Nimje (shashanknimje)]

Okay, this happened to me on Ubuntu 20.04.1 LTS. Then it happened to me on 20.04 LTS. This happened several times. What worked for me is unplugging my Ethernet cable and disconnecting my WiFi, and unchecking the "update the OS while installing" something option. Making sure that my computer was not on the internet before starting the installation process did the trick. Hope this helps someone.

[Nguyen Duy Tuan (ndtuan20)]

Error on install Dell Precision 7510

[Damien Thébault (damien-thebault)]

Occurs to me in a daily CI/CD vagrant build since Sep 23, 2020 3:30 AM:

    default: Processing triggers for libc-bin (2.31-0ubuntu9) ...
    default: E
    default: :
    default: Could not configure 'libc6:i386'.
    default: E
    default: :
    default: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)

[Mikael Ståldal (mikaelstaldal)]

I just got this error when installing ubuntu-20.04.1-desktop-amd64.iso from USB stick on Lenovo Think Pad X1 Extreme Gen 2 I9.

[Calvin Christian (calvinchrst)]

Hi, I just got this error when installing Ubuntu 20.04.1 LTS from USB Drive.
My laptop details are below:
Model: Illegear Onyx V Ryzen
Processor: AMD Ryzen 7 4800H with Radeon Graphics 2.90 GHz
RAM: 16GB
System Type: 64-bit, x-64 based processor

[Julian Andres Klode (juliank)]

Hey people, adding "me too" comments does not add anything useful to the bug. Please click the "affects me" kind of button at the top instead if you want to express your being affected.

[Jakob R (jraitzyk)]

I updated my Xubuntu system 2 days ago but only rebooted last night, and now my system won't boot.
So I tried to reinstall, had it download updates during installation, and the installer crashed and sent me here.

was installing Xubuntu 20.04.1 LTS from USB on:
2013 Alienware Aurora
some i7 (ivy or sandy bridge)
GTX 660ti

[Balint Reczey (rbalint)]

Adding the regression-update tag because the issue in APT is triggered by the SRU of glibc. It is not a result of a change in glibc, rather than of glibc having been updated.

[Alyana (alyana)]

I can confirm that.

Installation fails on a Notebook with Intel I7-4712MQ and Nvidia GeForce 840M.

Failed both with 20.04 LTS and 20.04.1 LTS with the option to install the additional drivers and codecs checked.

Installation succeeded with 20.04.1 LTS when NOT choosing to install the additional drivers.

[Alyana (alyana)]

Forgot to mention, that I tested that with Ubuntu 20.04 and 20.04.1

[Claus Appel (spectrumdt)]

I have a similar problem. For me the Ubuntu 20.04 installer would consistently crash at 90% (regardless of which hard drive I installed it to). When I followed the instructions to report the bug, it led me here.

I was able to circumvent the problem by choosing "minimal installation" and NOT "download updates while installing". That made the installation succeed.

It might be caused by bad hardware on my system. I don't know.

[Boz (bozybosman)]

I have a similar problem. Directed here after a fresh install crashed.

I had selected 'install additional drivers'.
I did not have the 'minimal install' checked.

I will try to reinstall unchecking each and report back.

Information:
USB boot from Ubuntu 20.04.1 LTS ISO.

Processor: AMD FX(tm)-6100 Six-Core Processor
Storage: 2TB Hitachi HUA72302
Display: TU106 [GeForce RTX 2070]

@Steve Langasek: I have lshw information for my system. My system is a bit of a mix. As I am fairly new to all of this I wasn't sure it was a good idea to post that sort of detailed data here. Message me if the information on my system would help.

[exploiTED (tmeralus)]

New crash on my end

Device Information:
Dell G5 15 5587
Service Tag: B9WHYQ2
Graphics: NVIDIA GeForce GTX1050 Ti
16gb ram
128gb NAND SSD
1TB SSD

I tried installing the ubuntu-20.04.1-desktop-amd64.iso
Image today 09-26-2020 and had the installer crash and bring me here...so hi guys.

Not sure the name of the iso image or version other than that it came from releases.ubnuntu.com
Last modified: 2020-07-31 16:52

*Installed with internet (wifi)
• Selected install 3rd party devices
Wiped hard drive of previous 18.04 image.

Tried installing on two hard drives
Root "/" dir on 128gb
Home "/home" on 1tb ssd

128gb ssd has the following
1024 /boot partition
2048 swap area
The rest of the partition is for root dir "/"

Bug report sent me here after the crash.
Going to attempt offline and no 3rd party install.

[exploiTED (tmeralus)]

The installation finished successfully with no internet connection and no 3rd party software installed but the system doesn't boot to grub (different from this bug report but an update to the installation nonetheless).

Details again:
Device Information:
Dell G5 15 5587
Service Tag: B9WHYQ2
Graphics: NVIDIA GeForce GTX1050 Ti
16gb ram
128gb NAND SSD
1TB SSD

[Georgi Nikolov (gnikolov359)]

Same issue here, I was trying to do a fresh install with option to install 3rd parties only and no updates.

```
System:
  Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
  Desktop: KDE Plasma 5.18.5 Distro: Ubuntu 20.04.1 LTS (Focal Fossa)
Machine:
  Type: Desktop Mobo: Gigabyte model: B450 AORUS M v: x.x serial: <filter>
  UEFI: American Megatrends v: F50 date: 11/22/2019
CPU:
  Topology: 8-Core model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: Zen
  L2 cache: 4096 KiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 124563
  Speed: 2195 MHz min/max: 2200/3900 MHz Core speeds (MHz): 1: 2194 2: 2195 3: 2195
  4: 2190 5: 2196 6: 2188 7: 2186 8: 2196 9: 2195 10: 2192 11: 2195 12: 2195
  13: 2195 14: 2196 15: 2195 16: 2190
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: Gigabyte driver: nouveau
  v: kernel bus ID: 07:00.0
  Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa
  resolution: 1920x1080~60Hz
  OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8
  direct render: Yes
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: Gigabyte
  driver: snd_hda_intel v: kernel bus ID: 07:00.1
  Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel
  v: kernel bus ID: 09:00.4
  Device-3: C-Media USB PnP Audio Device type: USB
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 5-2:2
  Sound Server: ALSA v: k5.4.0-42-generic
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
  driver: r8169 v: kernel port: e000 bus ID: 04:00.0
  IF: eno1 state: down mac: <filter>
  Device-2: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee
  v: kernel port: d000 bus ID: 06:00.0
  IF: wlp6s0 state: down mac: <filter>
  IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac: <filter>
Drives:
  Local Storage: total: 2.30 TiB used: 6.75 GiB (0.3%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB size: 465.76 GiB
  ID-2: /dev/sda vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB temp: 36 C
  ID-3: /dev/sdb type: USB vendor: Samsung model: Flash Drive size: 29.88 GiB
Partition:
  ID-1: / size: 15.69 GiB used: 614.5 MiB (3.8%) fs: overlay source: ERR-102
  ID-2: /var/log size: 26.92 GiB used: 55.1 MiB (0.2%) fs: ext4 dev: /dev/sdb3
  ID-3: swap-1 size: 3.72 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p6
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: nouveau temp: 33 C
  Fan Speeds (RPM): N/A gpu: nouveau fan: 726
Info:
  Processes: 315 Uptime: 24m Memory: 31.37 GiB used: 2.59 GiB (8.2%) Init: systemd
  runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.17 inxi: 3.0.38

```

[exploiTED (tmeralus)]

The installation finished successfully with no internet connection and no 3rd party software installed but the system doesn't boot to grub (different from this bug report but an update to the installation nonetheless).

Details again:
Device Information:
Dell G5 15 5587
Service Tag: B9WHYQ2
Graphics: NVIDIA GeForce GTX1050 Ti
16gb ram
128gb NAND SSD
1TB SSD

[timandjulz (fromubuntu-timandjulz)]

I reproduced this with:
o. 10GB network card - Connected to network but with no DHCP on the network. This is a card I normally hard wire to direct connect to my NAS
o. 1GB network card - Connected to a network with DHCP

First attempt failed with this error.

On the second attempt, I disconnected the 10GB network card and reinstalled. / was reformatted. /boot was an existing boot and was not reformatted. The second attempt worked.

[timandjulz (fromubuntu-timandjulz)]

Delete comment #63. I was unable to reproduce it working after disconnecting the 10GB network adapter.

[Boz (bozybosman)]

I am not sure if this helps but I found that a "normal" installation with the third party install and driver update checkboxes unchecked worked for me. I posted my scenario above.

Once OS was setup I tried to install my graphics drivers manually. I saw that a very similar error while doing this and thought I would feed it back in case it helps. Apologies in advance as I didn't think to record all the output from the terminal. I've included the relevant section of history instead.

   12 sudo apt install nvidia-settings
   13 nvidia-settings
   15 sudo apt remove nvidia-settings
   16 sudo apt purge nvidia-settings
   17 apt search nvidia-driver*
   20 sudo apt install nvidia-driver-450 nvidia-settings
   23 sudo apt install libc6:i386
   26 sudo apt remove nvidia-driver-450 nvidia-settings
   27 sudo apt install libc6:i386
   28 sudo apt install nvidia-driver-450 nvidia-settings
   29 nvidia-settings

Line 12/13 gave an error stating that I didn't have a driver. so I removed the nvidia-settings.
line 20 is where I tried to install the new driver. This gave an error to do with libc6:i386 which made me think of this bug log, hence i am posting it here.
Line 23 I installed this libc6:i386 thing separately as suggested above. it seemed to work
I removed and reinstalled the driver and everything seems to work.

Obviously, I did have to download the driver from nvidia's website before the install of the driver would work.

The missing lines of history are my naivety using terminal commands if a full history helps I have this but without the output side I doubt it's of use.

so thanks to Vadim Zeitlin (vz-ubuntu) for the suggestion.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[jimbean (clebon-deactivatedaccount)]

Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
tried ubuntu 20.04
tried ubuntu 20.04.1
this has happened twice on my i3 4130 processor dual boot windows 8.1

it happened after i visited some new web sites that i have never visited before from windows 8.1

the computer i3 4130 locks up when trying to boot to latest kernel
so i booted to last known working kernel
it boots up
but is giving me all kinds of errors
so i downloaded ubuntu 20.04.1 and tried to install
same error cant install ubuntu
seems like a boot sector virus ????????

[Le Tran Bao Loc (dominiclc)]

A little update. So I just got this annoying bug where it said the installer crashed. I reported the bug and went on restarting my PC. It actually works fine now... I don't know if something bad may happen in the future. Can anyone let me know? What should I do?

[becky segura (youngjhawk)]

Was on a version of 20.04 Xubuntu, accepted an upgrade for 20.04.1 and then it said could only partial upgrade. I reluctantly did the partial upgrade and after had issues with a nvidia.ko/nvidia modeset.ko mismatch and machine would no longer boot. After several hours of trying to purge/reinstall drivers, etc, I did a fresh install of 20.04.1 and was directed to this page after. I, too, chose the normal install with 3rd party updates and driver updates checked. ZFS also chosen.

ASRock B450
GT 710
Ryzen 5

Sep 27 19:58:50 xubuntu ubiquity: #015
Sep 27 19:58:55 xubuntu /plugininstall.py: Verifying downloads ...
Sep 27 19:58:55 xubuntu /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
Sep 27 19:58:55 xubuntu /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found."
Sep 27 19:58:55 xubuntu /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
Sep 27 19:58:55 xubuntu /plugininstall.py: Downloads verified successfully
Sep 27 19:58:55 xubuntu /plugininstall.py: Exception during installation:
Sep 27 19:58:55 xubuntu ubiquity: Error in function: install
Sep 27 19:58:55 xubuntu /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
Sep 27 19:58:55 xubuntu /plugininstall.py:
Sep 27 19:58:55 xubuntu ubiquity: Get:61 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 libva-wayland2 amd64 2.7.0-2 [8924 B]
Sep 27 19:58:55 xubuntu ubiquity: #015Get:62 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 gstreamer1.0-vaapi amd64 1.16.2-2 [323 kB]

[Luca Passini (lucapassini)]

Since it has been marked as "Fix Released", what are the required steps to follow in order to bypass the installation crash? Thanks.

[Balint Reczey (rbalint)]

@toipon Please don't change the status of the bug to wrong values.

[Black Mage Zeraf (blackmagezeraf)]

Tried Installing using UNetBootin on my secondary hard drive and got this error

[jimbean (clebon-deactivatedaccount)]

booted to windows 8.1 deleted linux partition
coverted it to ntfs
had windows 8.1 expand and include the old deleted linux partition
now it lets me install the 20.04.1 iso to a point where it says failed to install , but i can boot it off of my dual boot ssd installation ????
but its is basically still in bad shape for an operating system needs alot of tweaking to get to run properly
i believe the problem is in the windows boot loader ?????

[jimbean (clebon-deactivatedaccount)]

ok used windows 8.1 repair disk to fix efi bootloader not that good with computers
maybe i got it right and used windows 8.1 repair disk to fix mbr
it still did not let my machine install ubuntu 20.04.1 without crashing at end of installation
but i pull the usb boot iso and reboot and the grub menu is there and i can run both ubuntu and windows
every time i post here i have tried different solutions 3 or 4 times
but please don not try what i have tried

[Anthony Man (antmanguy)]

Installation successful by turning off WiFi, not checking 'download updates while installing ubuntu' and not checking 'install third-party software for graphics and WiFi hardware and additional media formats'. Once your installation is complete, if you connect to WiFi, ubuntu will request software updates, which you can allow then.

[Nick Moyer (nipamo)]

I followed the same steps as Anthony Man above and it was successful.

[Peter Freeman (petersfreeman)]

I am just installing the daily build from 2020-09-28 of Ubuntu 20.10 (Groovy Gorilla). I received this error right at the end of installation. It screwed up my nvidia settings and I had to manually re-install the nvidia drivers. Everything appears to be working fine now, though I haven't stress-tested the new system yet.

[Henry F Tew (henry-ubuntew)]

Installed correctly the first time. Upon reinstall, received this issue.

[Balint Reczey (rbalint)]

I'm giving a try to dropping libc6's libcrypt1's dependency and if that works this will work around the issue in Focal but not in Groovy because libc6 also depends on libnss-nis and libnss-nisplus there. Ideally the bug could be fixed in APT in Groovy.

[Nguyen Khanh Long (longengie)]

I got this problem when install Ubuntu too. My laptop have NVIDIA graphic card and secure boot disabled. The installer see the error but when I remove and reboot laptop, Ubuntu installed on laptop but missing NVIDIA XServer Settings. But funny thing that it's appear on my Ubuntu boot media that using 20.04.1 version but giving no error in last time. So maybe the NVIDIA package from internet have problem (I'm not specialize in Linux but still know something about computer). Maybe this information can help.

[Steve Langasek (vorlon)]

Do not touch the state of the tasks on this bug if you are not a developer.

[lesbats fabrice (flesbats)]

I have re-install ubuntu 18.10 (USB live) with 'install third-party software for graphics and WiFi hardware and additional media formats'
=> ok
I launch the update to 20.04 and ALL is OK now !!
(nvidia card is recogniezd by system.)

Asus X93S with nvidia Gforce GT 630M

[Balint Reczey (rbalint)]

It does not seem possible to fix the bug in glibc, please use the daily installer images at http://www.cdimage.ubuntu.com/focal/daily-live/current/ until APT gets fixed on the release image.

The daily installer images has the latest libc6 packages already thus the i386 version can be safely installed even with the current APT.

[CryptoJones (cryptojones)]

If you don't select "Install Third-Party Drivers" it works fine.

[Tim Wetzel (twetzel21)]

Note that this bug also affects efforts to install older images, including 20.04 from May and June of this year: those installs crash also with this same error. This matters, because the bugs introduced by Updater changes since mid-September have made Ubuntu troublesome and unstable. Bugs that have occurred or recurred since mid-September include 1872159 (Booting with splash hangs when external monitors are connected); 1835660 (Initramfs unpacking failed); 1897185 (Login triggers suspend after update); and then this one (1871268) when trying to reinstall to regain stability. Not a good situation at all.

[John (john0990)]

I have this issue as well on a Lenovo T420s installing a freshly downloaded 20.04.01 LTS image. What's the easiest way to post or collect logs in such cases?
I wanted to upload all logs but I can add only a single attachement to this message.

[John (john0990)]

installer version: ubiquity 20.04.15.2

[John (john0990)]

Found a lot reports via google looking up "XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0), but by uid 999! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)"
(last ubuntu ubiquity message at Oct 3 19:36:03 from syslog line https://launchpadlibrarian.net/500526443/syslog) which could be related

[Jon Brase (jonathan-brase)]

I have encountered this issue trying a fresh install of Kubuntu 20.04.1. The entire reason that I tried a fresh install is that trying to upgrade my existing system from Ubuntu Mate 18.04 to 20.04 resulted in the upgrade finishing with errors and leaving my system in an unusable state (fortunately, I have a full backup, so rolling back a failed upgrade is painless, other than the time consumed). I don't know if the root cause of both issues is the same or not.

My graphics card is an NVidia GeForce GTX 750 Ti. /var/log/syslog from the failed ground-up installation is attached (I attempted installing twice in the live session with failures both times). I will attempt to find time to retry the upgrade and attach the syslog from that so we can see if the root cause is the same (I have already rolled the filesystem back from backup for the previous attempts, so I don't have a syslog for them).

The end result is that I have no upgrade path from 18.04 to 20.04.

[Curtis Schroeder (publicpanther)]

Well, I see the 20.04.1 live image still has a problem installing (NVIDIA?) drivers during the initial install that was in the original 20.04 release. I shall try again without the drivers install option. I was trying a minimal clean install this time if that makes any difference for the analysis.

[Alessio (starbyte)]

No Matter now. Thank you.
I simpl complete installation without chosing no option and let the program start by itself and tell not to do download updates during installation.
Now installation is complete, system works and tomorrow i do all the updates and let you know.
Thanks for support. Bye !

> Il 04/10/2020 21:57 Curtis Schroeder <email address hidden> ha scritto:
>
>
> Well, I see the 20.04.1 live image still has a problem installing
> (NVIDIA?) drivers during the initial install that was in the original
> 20.04 release. I shall try again without the drivers install option. I
> was trying a minimal clean install this time if that makes any
> difference for the analysis.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871268
>
> Title:
> Installation fails when "Install Third-Party Drivers" is selected
>
> Status in GLibC:
> New
> Status in Ubuntu CD Images:
> Fix Released
> Status in apt package in Ubuntu:
> Confirmed
> Status in glibc package in Ubuntu:
> Invalid
> Status in apt source package in Bionic:
> Confirmed
> Status in glibc source package in Bionic:
> Fix Released
> Status in apt source package in Focal:
> Confirmed
> Status in glibc source package in Focal:
> Invalid
>
> Bug description:
> Please use the latest daily installer images if you would like to enable third-party drivers during installation:
> http://www.cdimage.ubuntu.com/focal/daily-live/current/
>
> [Original Bug Text]
>
> Test Case
> 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers
> 2. Proceed with installation
>
> The following error message is displayed in /var/log/syslog
> /plugininstall.py: Verifying downloads ...
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libs...

[Alessio (starbyte)]

No Matter now. Thank you.
I simpl complete installation without chosing no option and let the program start by itself and tell not to do download updates during installation.
Now installation is complete, system works and tomorrow i do all the updates and let you know.
Thanks for support. Bye !
> Il 04/10/2020 13:15 Jon Brase <email address hidden> ha scritto:
>
>
> ** Attachment added: "The attachment for my comment above does not seem to have taken. This is /var/log/syslog for a failed ground-up Kubuntu 20.04 installation"
> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871268/+attachment/5417422/+files/syslog
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871268
>
> Title:
> Installation fails when "Install Third-Party Drivers" is selected
>
> Status in GLibC:
> New
> Status in Ubuntu CD Images:
> Fix Released
> Status in apt package in Ubuntu:
> Confirmed
> Status in glibc package in Ubuntu:
> Invalid
> Status in apt source package in Bionic:
> Confirmed
> Status in glibc source package in Bionic:
> Fix Released
> Status in apt source package in Focal:
> Confirmed
> Status in glibc source package in Focal:
> Invalid
>
> Bug description:
> Please use the latest daily installer images if you would like to enable third-party drivers during installation:
> http://www.cdimage.ubuntu.com/focal/daily-live/current/
>
> [Original Bug Text]
>
> Test Case
> 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers
> 2. Proceed with installation
>
> The following error message is displayed in /var/log/syslog
> /plugininstall.py: Verifying downloads ...
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found."
> /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2...

[bernd (triggetry)]

Is not installing third party drivers during OS installation and doing an apt-get update/upgrade and installing third party drivers at this point a suitable workaround? Would this work?

[Winston Fan (franva)]

Hit the same issue on 6th Oct 2020.

I downloaded the latest ISO from Ubuntu official website and created my bootable USB to install the latest 20.04 version.

The crash happened towards the end of installation, 80% in progress.

My PC specs:
AMD Ryzen X3700
NVIDIA RTX 2080Ti, Gigabyte
Kingston A2000 1TG M.2 NVME SSD
RAM 64GB

The File system I chose during partitioning is:
Btrfs
Mount Point: /

Hopefully this issue will be solved soon.

For now, what should I do?
reinstall the Ubuntu 20.04?

[Tim Wetzel (twetzel21)]

Sorry to say that I tried to install from images from both May and June of this year, obviously 20.04. Both failed with the same crash. And, like you, I need nvidia and other specific drivers.

Even if you can get past the crash, other changes that have been made since mid-September are wreaking havoc also:
-there are problems with the new compression algorithm for initramfs
-there are issues with startup hanging with a spinning Ubuntu logo, forcing hard power down
-there are issues with startup going into suspend as soon as the login password is entered

I too hope that this gets solved soon.

[Andy Wharton (andywharton)]

Installing from the latest daily installer fails when installing grub-efi-amd64 as it has unmeet dependencies:

grub-common and grub2-common give a warning about 2.04-1ubuntu26.4 being required, but 2.04-1ubuntu26.5 is to be installed.

[Mohammad Mahdi Sharafi (mahdish)]

I used the latest ubuntu installer but it happened again!!!

[Alex (errantscientist)]

I've just used the 20.04.1 installer. Connected to the internet during installation, chose full installation, upgrade during installation and third-party drivers. I'm on an old intel and Nvidia, 650 TI as far as I remember. Crashed in about 85% of completion. My first Ubuntu installation, so would like to know if I should reinstall with different settings or fix it as is. Don't expect anyone to answer tho...

[Balint Reczey (rbalint)]

@errantscientist Please read the first line of the bug description...

[Balint Reczey (rbalint)]

@mahdish The daily image as recommended at the first line of the bug description?

[Tim Wetzel (twetzel21)]

I already used the daily image; and yes I got the (re)installation to complete without crashing. BUT the freshly (re)installed Ubuntu system remained unstable and therefore unusable due to other bugs that were introduced or re-introduced by the two Ubuntu Updater packages pushed out since mid-September. Even with the fresh re-installation from the daily image, I still have:

-there are problems with the new compression algorithm for initramfs
-there are issues with startup hanging with a spinning Ubuntu logo, forcing hard power down
-there are issues with startup going into suspend as soon as the login password is entered

These were why I did a full erase and re-install of Ubuntu to start with: these bugs had, in the week or two prior, made Ubuntu frighteningly unstable. I too hope that this all gets solved soon.

There are bug reports on all of these: see bugs #1872159, 1835660, 1897185. There are related and/or duplicates of some of these also.

[Tim Wetzel (twetzel21)]

I should add that, in researching old posts on these issues, I gather that nVidia driver(s) have been a factor; so note that the last Ubuntu Updater package prior to all this did also include an update to the nVidia driver package.

[Damien Thébault (damien-thebault)]

My CI/CD now works properly since this morning (see #48).
And it's using the same base image (bento/ubuntu-20.04 202008.16.0) so there is indeed a working fix on the apt servers side.
Regards

[Balint Reczey (rbalint)]

The update of the gcc-10 packages have made APT take a different installation path avoiding hitting this bug. The APT bug is still not resolved, but it does not affect any installation methods in 20.04 anymore.

[Thiago Ferreira Do Nascimento (thiagofdnascimento99)]

I have Nvidia card and this error happened after marking the option to install 3rd party drivers. Once before I installed without 3rd party drivers and I could finish the installation after boot but nothing happened after I can`t even open the tty to try solve the problem.

[Tim Wetzel (twetzel21)]

These bugs started with a Ubuntu update just prior to Sept 14 (see post 103 above). By the 14th, there were initramfs problems on startup and the hang on spinning circle which forced hard power downs.

Then on Sept 24, more updates installed including updates to grub, *nvidia drivers*, and some other things. Immediately following these Sept 24 updates, the suspend after entering login password started. That first machine affected subsequently became so unstable that I tried to reload Ubuntu; but that failed due to this bug. So that machine is now completely sidelined.

These 4 bugs are devastating my Ubuntu machines. PLEASE fix these (again, this bug and the other 3 mentioned in post 103)!

And please NOTE that the updated nvidia driver packet DOES seem to be one of the bad actors in all this?

[steveahart (steveahart)]

Downloaded the latest 20.04.1 iso today. Performed a clean install which hit the error at the end of the install. Was redirected to this bugreport.

System configuration:
Main graphics running through NVIDIA GTX 1080Ti
Intel core i7-4790 CPU 3.6GHz
16 GB memory
Z97 Extreme6 motherboard
Samsung SSD 850 EVO 250GB

[steveahart (steveahart)]

Removed NVIDIA card, re-ran full install with no problems. Reinstalled card, then installed NVIDIA/CUDA from ubuntu repos and all is fine.

[John Caron (jlcaron)]

Using 20.04.1 LTS that I downloaded 11/14/2020, I created an install USB, and did a clean install on an HP Z440 with Nvidia 310 (GF119 [NVS 310]). I checked "download updates" and "install 3rd party software".

The install crashed and directed me to this bug. Attached is the syslog, there was no /var/logs/install directory.

Using the same install USB, I did another clean install, replacing everything. This time I unselected "download updates" and "install 3rd party software". The install worked fine and the default nouveau graphics driver seems to be fine. I will add another comment in order to upload the syslog from that install.

I have not yet tried to update or restart, that will be next.

[John Caron (jlcaron)]

Heres the syslog from the install that worked, with "download updates" and "install 3rd party software" disabled.

[Tianon Gravi (tianon)]

I think the core of this is fixed, but there's some situations still where it triggers -- here's a new reproducer that can still trigger it reliably with Docker (since I can't reproduce with the simplified steps in #31 anymore):

```
$ docker pull ubuntu:20.04

20.04: Pulling from library/ubuntu
Digest: sha256:bc2f7250f69267c9c6b66d7b6a81a54d3878bb85f1ebb5f951c896d13e6ba537
Status: Image is up to date for ubuntu:20.04
docker.io/library/ubuntu:20.04

$ docker run --rm ubuntu:20.04 sh -c 'dpkg --add-architecture i386 && apt-get update -qq && apt-get install -y libc6:i386 libfontconfig1:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:i386'

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  fontconfig-config fonts-dejavu-core gcc-10-base gcc-10-base:i386
  libatomic1:i386 libbsd0:i386 libcrypt1:i386 libdrm-amdgpu1:i386
  libdrm-common libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386
  libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi7:i386
  libfreetype6:i386 libgcc-s1 libgcc-s1:i386 libgl1:i386 libglapi-mesa:i386
  libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libidn2-0:i386 libllvm10:i386
  libpciaccess0:i386 libpng16-16:i386 libsensors-config libsensors5:i386
  libstdc++6 libstdc++6:i386 libtinfo6:i386 libunistring2:i386 libuuid1:i386
  libvulkan1:i386 libwayland-client0:i386 libx11-6:i386 libx11-data
  libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
  libxcb-glx0:i386 libxcb-present0:i386 libxcb-randr0:i386 libxcb-sync1:i386
  libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386
  libxshmfence1:i386 libxxf86vm1:i386 libzstd1:i386 mesa-vulkan-drivers:i386
  ucf uuid-runtime zlib1g zlib1g:i386
Suggested packages:
  glibc-doc:i386 locales:i386 pciutils:i386 lm-sensors lm-sensors:i386
The following NEW packages will be installed:
  fontconfig-config fonts-dejavu-core gcc-10-base:i386 libatomic1:i386
  libbsd0:i386 libc6:i386 libcrypt1:i386 libdrm-amdgpu1:i386 libdrm-common
  libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386
  libedit2:i386 libelf1:i386 libexpat1:i386 libffi7:i386 libfontconfig1:i386
  libfreetype6:i386 libgcc-s1:i386 libgl1:i386 libgl1-mesa-dri:i386
  libgl1-mesa-glx:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386
  libglx0:i386 libidn2-0:i386 libllvm10:i386 libpciaccess0:i386
  libpng16-16:i386 libsensors-config libsensors5:i386 libstdc++6:i386
  libtinfo6:i386 libunistring2:i386 libuuid1:i386 libvulkan1:i386
  libwayland-client0:i386 libx11-6:i386 libx11-data libx11-xcb1:i386
  libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386
  libxcb-present0:i386 libxcb-randr0:i386 libxcb-sync1:i386 libxcb1:i386
  libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386
  libxshmfence1:i386 libxxf86vm1:i386 libzstd1:i386 mesa-vulkan-drivers:i386
  ucf uuid-runtime zlib1g:i386
The following packages will be upgraded:
  gcc-10-base libgcc-s1 libstdc++6 zlib1g
4 upgraded, 61 newly installed, 0 to remove and 0 not upgraded.

...

Processing triggers for libc-bin (2.31-0ubuntu9.1) ...
E: Could not configure 'libc6:i386'.
E: Could not perform immedi...

[Julian Andres Klode (juliank)]

@Balint The Debian bug is different - it's single arch

[Julian Andres Klode (juliank)]

as in, the fix for this bug does not fix the Debian one.

[Julian Andres Klode (juliank)]

Given more and more issues popping up even without multi-arch, I've decided to downgrade the late error to a warning.

[Tim Wetzel (twetzel21)]

I am seeing much better stability of the Ubuntu distro today. I am working with a reinstallation from a 20.04.1 image from late August; I loaded it about a week ago hoping to recover from the 4 bugs I've been dealing with but still had problems. Today I ran Ubuntu Update AND went back to the open source nVidia driver (this is a T570 with both Intel and nVidia graphics).

I urge working with nVidia: their driver update near the end of September seemed to be the final straw in all of this, and making sure that driver is stable seems important to ensure that the installer is able to deliver a stable system. Otherwise these installation failures and stability problems may continue to haunt us.

[Julian Andres Klode (juliank)]

@Tim Your system stability is not relevant to this bug report about apt failing immediate configuration failing installs.

[Eason Yu (ieason8)]

@Julian I still encounter this issue about failing immediate configuration failing installs, or I need to verify it until it's marked as 'Fix Released'? Thanks!

[Timo Aaltonen (tjaalton)]

Hello andresgenovez, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.1.11 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-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted apt (2.1.11) for groovy have finished running.
The following regressions have been reported in tests triggered by the package:

sbuild/0.80.0ubuntu1 (amd64, arm64, s390x, ppc64el)
gcc-10/unknown (amd64, armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Launchpad Janitor (janitor)]

This bug was fixed in the package apt - 2.1.11

---------------
apt (2.1.11) unstable; urgency=medium

  [ JCGoran ]
  * Fix "extended_states" typo in apt-mark(8) (Closes: #969086)

  [ Julian Andres Klode ]
  * doc: Bump Ubuntu release from focal to groovy
  * Do not produce late error if immediate configuration fails, just warn
    (Closes: #953260, #972552) (LP: #1871268)

  [ Frans Spiesschaert ]
  * Dutch manpages translation update (Closes: #970037)

 -- Julian Andres Klode <email address hidden> Wed, 21 Oct 2020 11:53:18 +0200

[Simeon (simeon0806)]

Problem

[Simeon (simeon0806)]

Problem in istaling ubuntu

[Chad Kennow (ckennow)]

Failed installation. Dual boot configuration.

[jon anoter (jon8899888)]

same fail. literally last10 seconds fail error message. dual boot installation on two nvme drives
Acer Nitro5 AN5-15-55 pls help ,, is there a workaround? I been using Ubuntu last 8 yrs cant live without it. I triede 20.04 and 20.10 with install thrid party drivers elected and install updates not selected.

[Praveen pokuri (praveenpokuri3)]

what is release version fr this?

[Julian Andres Klode (juliank)]

We do not have a fix for this yet.

[Łukasz Zemczak (sil2100)]

As requested by the uploader, I will be dropping apt 2.1.11 from groovy-proposed. It will be superseeded by a newer version in the nearest future.

[Julian Andres Klode (juliank)]

2.1.12 will be landing in hirsute tomorrow-ish, once it syncs from Debian unstable. This fixes _this_ bug, namely immediate configuration of _foreign_ architecture packages, by disabling the code that forces them to be configured together with their native architecture siblings.

It does _not_ fix other instances that look like this bug where the package failing to be configured immediately is a native architecture package, nor does it fix issues where disabling immediate configuration causes the ordering to fail.

[dimas (ashestray-deactivatedaccount)]

failed install, tried in both ubuntu 20.04.1 and 20.10.
It works fine when I install ubuntu last time, for somewhat reason I nuke my LTS install and wanted to try 20.10 then get redirected into this page, then tried to get back to 20.04.1 install with another usb get redirected to this page as well. both same option with "Install third party software - enabled".

system : intel i7-9700KF and nVidia gtx1660,

[David Rincon Sanchez (david245789)]

Problems appear with changs on drivers for/and screen resolution

[Alx (sopadops)]

It happened with me today. Using latest release here:https://releases.ubuntu.com/20.10/. Last modified: 2020-10-22 14:31. It`s running apt 2.1.10, so haven`t tried with the `fixed` version \*This bug was fixed in the package apt - 2.1.11\

Any way to try a nightly build of the desktop image 20.10 with apt 2.1.12 to see if works? I can only find daily of 21.04. http://cdimage.ubuntu.com/daily-live/current/

system: intel i7-8700K and nVidia GeForce GTX 1080 Ti

[Alx (sopadops)]

Sorry, even better I guess: after installed failed, ubuntu live started. I obviously have the install option here. Any way I can update apt to 2.1.12 here, and then try to install?

[john lawton (jsl1)]

I do not understand how to proceed with my failed installation.IE is there a fix that works?

[Launchpad Janitor (janitor)]

This bug was fixed in the package apt - 2.1.12

---------------
apt (2.1.12) unstable; urgency=medium

  [ Julian Andres Klode ]
  * pkgnames: Correctly set the default for AllNames to false (LP: #1876495)
  * pkgnames: Do not exclude virtual packages with --all-names
  * Remove expired domain that became nsfw from debian/changelog
  * Do not immediately configure m-a: same packages in lockstep (LP: #1871268)

  [ Américo Monteiro ]
  * Portuguese manpages translation update (Closes: #968414)

  [ David Kalnischkies ]
  * Rename CMake find_package helpers to avoid developer warnings
  * Install translated apt-patterns(7) man pages
  * Remove ancient versions support from apts postinst
  * Update libapt-pkg6.0 symbols file
  * Refresh lintian-overrides of apt and libapt-pkg-doc

 -- Julian Andres Klode <email address hidden> Mon, 23 Nov 2020 17:52:37 +0100

[Perzan (perzan)]

I am having the same issue and was wondering where I can get these fixed versions? I tried the 20.10 ISO installation image from the main website, but I am still getting the same problem. I reckon there is some other repository I can grab the latest ISO installer to put on a thumb-drive using Rufus?

[Perzan (perzan)]

I will probably just switch back to 18.04 if not

[Alx (sopadops)]

Hi all. @jsl1 . I have found a workaround which worked for me.
- clean install
- usb stick with 20.10

1. boot usb
2. Select LIVE boot (don't install right away)
3. When in linux run apt update && apt upgrade
4. Run the install-linux on desktop
5. When asked, do no select "third party drivers"

This worked for me. After install, went in to settings and added third party drivers (nvidia)
All is working good.

system: intel i7-8700K and nVidia GeForce GTX 1080 Ti

[Tim Wetzel (twetzel21)]

With reference to post #132 above: If this is relevant to this issue.... I also am experiencing problems with switching drivers for the device on my systems that uses (or can use) a Ubuntu third party driver. Specifically nVidia for the GeForce 940MX. Changing between nVidia driver versions (all within the selections provided by Ubuntu's Updater) appears to succeed but driver performance is not correct. I restart after each driver change. I've seen screen tearing, freezing, video stuttering, etc while playing locally stored videos. I've used the same video file to test and the results remain unpredictable. Even going back to the generic xorg driver does not seem to fully stabilize performance of the 940MX. None of these issues were present prior to the mid-September Ubuntu updates associated with 20.04.1; and the nVidia driver(s) provided performance superior to the xorg version. Trying to reload Ubuntu in an attempt to squash these bugs triggered this crash bug. I obviously managed to work around it by NOT selecting third party drivers on install, but that necessitates changing the driver after install; and that has not worked well either.

If this is not relevant to this particular bug, then please disregard in deference to other bug reports. I provide this here only to assist by providing anecdotal observations in hopes that this may help in trying to resolve this third party driver related issue. And in the event that several of these bugs may be inter-related, please refer to also posts #84, 97, and 104 above regarding a group of bugs that all appeared following the mid-September Ubuntu LTS 20.04 updates; and note that there is a bug number (not listed above here) for the suspend on login issue, it is 1897185. Again: if this is not relevant to resolving this issue then disregard here.

Thank you.

[Tim Wetzel (twetzel21)]

Additional observation: I've tried using Ubuntu LTS 20.04 download images from July and August, selecting the option to install third party drivers. These images worked flawlessly at the end of the summer. But since the mid-September updates, even these earlier iso's of Ubuntu LTS 20.04 Desktop failed with this same install crash. So it would appear that there were changes in late September to things external to the Ubuntu download iso itself.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Josja Van Bever (josja)]

Crash happened on this dell latitude which I am supposed to use for my PhD.

Happened at the very end of the installation, when almost completely loaded.

Please contact me (<email address hidden>) for any possible solution. I am desperate.

[Josja Van Bever (josja)]

The crash mentioned in previous comment could (most probably?) be attributed to a (very small?) hardware failure of the usb stick used. Though, the same stick was used earlier in the same conditions to install ubuntu 18.

[Henry F Tew (henry-ubuntew)]

So, what IS the solution exactly????

On Thu, Dec 3, 2020 at 8:01 AM Josja Van Bever <email address hidden>
wrote:

> The crash mentioned in previous comment could (most probably?) be
> attributed to a (very small?) hardware failure of the usb stick used.
> Though, the same stick was used earlier in the same conditions to
> install ubuntu 18.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871268
>
> Title:
> Installation fails due to useless immediate configuration error when
> "Install Third-Party Drivers" is selected
>
> Status in Ubuntu CD Images:
> Fix Released
> Status in apt package in Ubuntu:
> Fix Released
> Status in apt source package in Bionic:
> Confirmed
> Status in apt source package in Focal:
> Triaged
> Status in apt source package in Groovy:
> Triaged
> Status in apt package in Debian:
> Unknown
>
> Bug description:
> [Impact]
> Installations that really succeeded would then fail because APT could
> not immediately configure a package. Which is a pointless way to fail at
> that point, because everything did work out anyway.
>
> So what we do is change that to a warning.
>
> [Test case]
> Not available right now. Issues can flare up and then disappear again.
>
> [Regression potential]
> It's imaginable that we missed something somewhere and some path that
> checked for a set error doesn't check it anymore, and we report success
> when we hit an error, but it seems unlikely.
>
> Behavior of --simulate changes. This used to fail before as well, and
> will now only produce a warning. We don't believe that is a reason of
> concern.
>
> [Groovy SRU]
> The groovy SRU is a sync of the 2.1.11 micro release from Debian
> unstable which also incorporates changes to the documentation: A typo fix,
> replacing focal with groovy in examples, and minor Dutch manual pages
> translation updates.
>
> We do not have test cases for the documentation changes, and we do not
> consider there to be a huge regression potential. As long as they
> build, they should be readable - maybe some words are wrong in the
> translation, who knows.
>
> [Original bug report]
> Test Case
> 1. Install Ubuntu Desktop on hardware with an nVidia card and select to
> install 3rd party drivers
> 2. Proceed with installation
>
> The following error message is displayed in /var/log/syslog
> /plugininstall.py: Verifying downloads ...
> /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version:
> '9.3.0-1ubuntu2' not found."
> /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb:
> "Version: '4.4.10-10ubuntu4' not found."
> /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version:
> '9.3.0-1ubuntu2' not found."
> /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version:
> '1.2.11.dfsg-2ubuntu1' not found."
> /plugininstall.py: Failed to find p...

[Matteo (matteoblombergghini)]

I solved this issue by
1) Not connecting to the internet while it installs
2) Not take any third party software in the process
other than that I followed the regular installation process, whipping my disk.

Took a lot of time for me to get the process working, but as far I can understand most of the reason was due to my processor (AMD® Ryzen 9 3900x) not having any graphical support, and my GeForce GTX 1650 not working.

Hope they figure out what went wrong in the process,

[William Chin (wmchin2003)]

Running on an MSI GT70 0ne. Bug that stops the installation right near the end.

[Alexander Selyutin (saga111a)]

I have similar issues - suddenly closed installation. Asrock z370 samsung 860 evo if it matters

[Zuhair (zackyboy)]

I got similar issue when I checked "Third Party" during install. I have Dell XPS 7590 with Nvidia 1650 graphics card

[Stephen Brandt (ztefn)]

I can add another "me too" on a Asus K73SV laptop with NVIDIA GeForce GT 540M. With "Install updates during install" and "Install third party drivers" checked I got the error which redirected me here. When I rebooted I was greeted with a black boot screen that not made it into GDM.

After installing again but this time without "Install third party drivers" checked the installation worked normally. Immediately was greeted with updates to install, though I had "Install updates during install" still checked.

I am very disappointed, especially since this issue has been known for over 8 months. This is the reason I wait some time before installing the new LTS. This should have been fixed in 20.04.1 already.

[Kishan Raj (kishanraj16)]

Installer Crashed Error

[Alexander Simonov (alexsimonov)]

I deselected Install third party software. This helped to install, but now the booting process hangs when a white circle is rotating on the start black screen.

[Scott Sanders (malgorath1)]

So 9 months almost after reporting this bug it is still happening on install. I expected better from Ubuntu that this, makes your entire 20.04 OS not worth even downloading if for this long you let a MAJOR flaw like this continue.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Julian Andres Klode (juliank)]

The first chance to fix it was in August, the next chance to fix it is in February. There's really no urgency here.

[Julian Andres Klode (juliank)]

There is an easy workaround, too: just don't check the box to install third party drivers.

[Jean-Baptiste Lallement (jibel)]

Your comment is not helpful. Not checking the box would not install nVidia drivers and your suggestion is not a valid workaround.

[Julian Andres Klode (juliank)]

You'll be able to install the driver after having rebooted and upgraded the distribution. You don't have to (and can't atm) do it _during_ install.

[Vitaliy Kosharskiy (kosharskiy)]

It's no matters when will you install the driver. Recent updates breaks somethings and my laptop freezes right after the boot. And i can't switch to any terminal because OS not respond. I haven't event a chance to read logs.
I investigated the problem and found that the problem somewhere in Xserver. The only way to successfully install Ubuntu it's not checking boxes with updates and third party drivers. If after successfully installation you will try to update packages OS wouldn't boot. I've tried to update each package manually and black screen appears after updating Xserver.

[Oliver Grawert (ogra)]

@kosharskiy this is completely unrelated to this installer bug (which is about configuring packages prior to/during install time), you should open a new bug for your issue ...

[Vitaliy Kosharskiy (kosharskiy)]

No, i'm faced this installer bug and it redirected me to this bug report. But i've found configuration when i can install OS, but i can't update my freshly installed system because it will not boot

[Burak (metinburak)]

Asus Ryzen 7 4800H geforce gtx 1660ti install third party drivers ubuntu 20.04 installation crashed and i have been directed here. Hope it will be solved in a short time. Very bad not to be able to install an OS directly to a user level pc in 2020 space flight age.

[Peter Klein (pdklein800)]

I have performed the installation several times. It only happens with either a BT 4 or a BT 5 dongle. Bluetooth 4 is CRS. Bluetooth 5 is mediatek.

[Jean-Baptiste Perrin (jbperrinnl)]

I got this same bug when trying to reinstall Ubuntu 20.10.04 LTS after a dual boot Windows install had killed my ubuntu. I have Nvidia and I did chose to download drivers during install. How do we solve this problem? Is there a valid workaround?

[Jean-Baptiste Perrin (jbperrinnl)]

Also I hate to say this but how on earth is this bug classified as "Fix Released" despite happening on a fresh Ubuntu image install?

[Eric Mintz (mintz-eric)]

Cannot contribute much because the desktop is completely blank (except for the background) and a black bar at the top. There is no "Activities" control. Even worse, the mouse pointer is the spinning Ubuntu disk. I can click on the date, which is right.

I will reboot and see what happens. Please wish me luck.

[Parker Grytdal (pgrytdal)]

Just hit this bug on Ubuntu MATE 20.10

[Parker Grytdal (pgrytdal)]

Tagging onto my previous post (https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/comments/167) I am on a Nvidia GTX 2060

[Laurent Zibell (laurentzib)]

Same problem with a Dell G5. Installing Ubuntu 20.04 from an USB stick with options "connected to the Internet" and "download third-party packages"

[Julian Andres Klode (juliank)]

I think we have the final fix now that covers every case and not just the corner case with libc6:i386. It now just ignores those errors, which as we can see works out fine in the end, because the failures occur after installing because the error was never correctly propagated to the caller.

A later code segment actually checks that everything is configured, so this is as safe as we can get, and best of all, it can't really regress stuff, since it does not change the actual ordering :)

[Łukasz Zemczak (sil2100)]

14:32 < juliank> sil2100: everything is straight forward cherry-picked from master, which is 2.1.18

[Łukasz Zemczak (sil2100)]

Hello andresgenovez, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.2 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-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. 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.

[Łukasz Zemczak (sil2100)]

Hello andresgenovez, or anyone else affected,

Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.4 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted apt (2.1.10ubuntu0.2) for groovy have finished running.
The following regressions have been reported in tests triggered by the package:

reprotest/0.7.15 (amd64, arm64, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted apt (2.0.4) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

gcc-10/10.2.0-5ubuntu1~20.04 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Leon Pappas (nephilim9)]

There definitely seems to be an issue here:

[ 88.448840] ------------[ cut here ]------------
[ 88.448842] nouveau 0000:01:00.0: timeout
[ 88.448887] WARNING: CPU: 3 PID: 1177 at
/build/linux-hwe-5.4-hNUtrM/linux-hwe-5.4-5.4.0/drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:313
nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau]
[ 88.448887] Modules linked in: cmac bnep snd_hda_codec_hdmi
snd_soc_hdac_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic
snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda
snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp
snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine nls_iso8859_1 joydev
hid_multitouch 8250_dw mei_hdcp intel_rapl_msr x86_pkg_temp_thermal
intel_powerclamp coretemp kvm_intel snd_hda_intel snd_intel_dspcfg uvcvideo
kvm iwlmvm snd_seq_midi snd_seq_midi_event snd_hda_codec videobuf2_vmalloc
rapl input_leds snd_hda_core snd_rawmidi mac80211 videobuf2_memops btusb
snd_hwdep videobuf2_v4l2 btrtl videobuf2_common asus_nb_wmi btbcm asus_wmi
btintel intel_cstate libarc4 serio_raw sparse_keymap wmi_bmof videodev
snd_seq snd_pcm bluetooth iwlwifi mc snd_seq_device snd_timer snd
processor_thermal_device mei_me ecdh_generic intel_rapl_common
intel_lpss_pci ecc
[ 88.448901] cfg80211 intel_lpss idma64 mei virt_dma soundcore
intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone
mac_hid int3400_thermal acpi_pad asus_wireless acpi_thermal_rel
sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4
algif_skcipher af_alg dm_crypt hid_generic usbhid nouveau i915
crct10dif_pclmul crc32_pclmul mxm_wmi ghash_clmulni_intel ttm i2c_algo_bit
aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect nvme
sysimgblt cryptd fb_sys_fops glue_helper drm r8169 ahci nvme_core realtek
libahci i2c_hid wmi video hid pinctrl_cannonlake pinctrl_intel
[ 88.448913] CPU: 3 PID: 1177 Comm: gnome-shell Not tainted
5.4.0-62-generic #70~18.04.1-Ubuntu
[ 88.448914] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming
FX705GE_FX705GE/FX705GE, BIOS FX705GE.302 11/16/2018
[ 88.448929] RIP: 0010:nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau]
[ 88.448930] Code: 45 b0 48 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 74
1b e8 3c 35 d6 c7 48 89 da 48 89 c6 48 c7 c7 ba c7 af c0 e8 2a 7f 70 c7
<0f> 0b eb a8 48 8b 1f eb e0 e8 fc 81 70 c7 66 90 66 2e 0f 1f 84 00
[ 88.448930] RSP: 0018:ffffb912c1447a08 EFLAGS: 00010282
[ 88.448931] RAX: 0000000000000000 RBX: ffff9b3ad8cfdb70 RCX:
0000000000000006
[ 88.448931] RDX: 0000000000000007 RSI: 0000000000000096 RDI:
ffff9b3add8d78c0
[ 88.448932] RBP: ffffb912c1447a58 R08: 00000000000003e9 R09:
0000000000000004
[ 88.448932] R10: 000000000000002c R11: 0000000000000001 R12:
ffff9b3aca5aab00
[ 88.448933] R13: 0000000000000010 R14: ffffffffffffff92 R15:
00000000ffffffff
[ 88.448933] FS: 00007ff79ae03ac0(0000) GS:ffff9b3add8c0000(0000)
knlGS:0000000000000000
[ 88.448934] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 88.448934] CR2: 000000c42085b000 CR3: 0000000850710002 CR4:
00000000003606e0
[ 88.448935] Call Trace:
[ 88.448950] ...

[Leon Pappas (nephilim9)]

I don't believe that this is fixed. I am still getting errors:

[ 88.448840] ------------[ cut here ]------------
[ 88.448842] nouveau 0000:01:00.0: timeout
[ 88.448887] WARNING: CPU: 3 PID: 1177 at
/build/linux-hwe-5.4-hNUtrM/linux-hwe-5.4-5.4.0/drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:313
nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau]
[ 88.448887] Modules linked in: cmac bnep snd_hda_codec_hdmi
snd_soc_hdac_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic
snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda
snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp
snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine nls_iso8859_1 joydev
hid_multitouch 8250_dw mei_hdcp intel_rapl_msr x86_pkg_temp_thermal
intel_powerclamp coretemp kvm_intel snd_hda_intel snd_intel_dspcfg uvcvideo
kvm iwlmvm snd_seq_midi snd_seq_midi_event snd_hda_codec videobuf2_vmalloc
rapl input_leds snd_hda_core snd_rawmidi mac80211 videobuf2_memops btusb
snd_hwdep videobuf2_v4l2 btrtl videobuf2_common asus_nb_wmi btbcm asus_wmi
btintel intel_cstate libarc4 serio_raw sparse_keymap wmi_bmof videodev
snd_seq snd_pcm bluetooth iwlwifi mc snd_seq_device snd_timer snd
processor_thermal_device mei_me ecdh_generic intel_rapl_common
intel_lpss_pci ecc
[ 88.448901] cfg80211 intel_lpss idma64 mei virt_dma soundcore
intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone
mac_hid int3400_thermal acpi_pad asus_wireless acpi_thermal_rel
sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4
algif_skcipher af_alg dm_crypt hid_generic usbhid nouveau i915
crct10dif_pclmul crc32_pclmul mxm_wmi ghash_clmulni_intel ttm i2c_algo_bit
aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect nvme
sysimgblt cryptd fb_sys_fops glue_helper drm r8169 ahci nvme_core realtek
libahci i2c_hid wmi video hid pinctrl_cannonlake pinctrl_intel
[ 88.448913] CPU: 3 PID: 1177 Comm: gnome-shell Not tainted
5.4.0-62-generic #70~18.04.1-Ubuntu
[ 88.448914] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming
FX705GE_FX705GE/FX705GE, BIOS FX705GE.302 11/16/2018
[ 88.448929] RIP: 0010:nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau]
[ 88.448930] Code: 45 b0 48 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 74
1b e8 3c 35 d6 c7 48 89 da 48 89 c6 48 c7 c7 ba c7 af c0 e8 2a 7f 70 c7
<0f> 0b eb a8 48 8b 1f eb e0 e8 fc 81 70 c7 66 90 66 2e 0f 1f 84 00
[ 88.448930] RSP: 0018:ffffb912c1447a08 EFLAGS: 00010282
[ 88.448931] RAX: 0000000000000000 RBX: ffff9b3ad8cfdb70 RCX:
0000000000000006
[ 88.448931] RDX: 0000000000000007 RSI: 0000000000000096 RDI:
ffff9b3add8d78c0
[ 88.448932] RBP: ffffb912c1447a58 R08: 00000000000003e9 R09:
0000000000000004
[ 88.448932] R10: 000000000000002c R11: 0000000000000001 R12:
ffff9b3aca5aab00
[ 88.448933] R13: 0000000000000010 R14: ffffffffffffff92 R15:
00000000ffffffff
[ 88.448933] FS: 00007ff79ae03ac0(0000) GS:ffff9b3add8c0000(0000)
knlGS:0000000000000000
[ 88.448934] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 88.448934] CR2: 000000c42085b000 CR3: 0000000850710002 CR4:
00000000003606e0
[ 88.448935] Call Trac...

[Leslie Satenstein (lsatenstein)]

Tried to install 2021-01-17... Failure. But I could get into terminal mode. What to add to complete the installation.

It would be useful to have a patch/script file that I could run in terminal mode that would perform all the corrections.

[Julian Andres Klode (juliank)]

I updated my focal to 2.0.4 and groovy to 2.1.10ubuntu0.2, and ran /usr/lib/apt/planners/apt on the eipp.log file and there are no errors any more.

[Launchpad Janitor (janitor)]

This bug was fixed in the package apt - 2.1.10ubuntu0.2

---------------
apt (2.1.10ubuntu0.2) groovy; urgency=medium

  [ JCGoran ]
  * Fix "extended_states" typo in apt-mark(8) (Closes: #969086)

  [ Jordi Mallach ]
  * Fix typo in Catalan translation.

  [ Julian Andres Klode ]
  * doc: Bump Ubuntu release from focal to groovy
  * pkgnames: Correctly set the default for AllNames to false, and do not
    exclude virtual packages if --all-names is specified (LP: #1876495)
  * Remove expired domain that became nsfw from debian/changelog
  * patterns: Terminate short pattern by ~ and ! (LP: #1911676)
  * Improve immediate configuration handling (LP: #1871268)
    - Do not immediately configure m-a: same packages in lockstep
    - Ignore failures from immediate configuration. This does not change the
      actual installation ordering - we never passed the return code to the
      caller and installation went underway anyway if it could be ordered at a
      later stage, this just removes spurious after-the-fact errors.

  [ Frans Spiesschaert ]
  * Dutch manpages translation update (Closes: #970037)

  [ Américo Monteiro ]
  * Portuguese manpages translation update (Closes: #968414)

  [ Helge Kreutzmann ]
  * German program translation update (Closes: #977938)

  [ Vangelis Skarmoutsos ]
  * Greek program translation update

 -- Julian Andres Klode <email address hidden> Thu, 14 Jan 2021 12:29:25 +0100

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package apt - 2.0.4

---------------
apt (2.0.4) focal; urgency=medium

  [ Julian Andres Klode ]
  * Merge 2.0.2ubuntu0.1 and 2.0.2ubuntu0.2 security updates with 2.0.3
    release.
  * pkgnames: Correctly set the default for AllNames to false, and do not
    exclude virtual packages if --all-names is specified (LP: #1876495)
  * Remove expired domain that became nsfw from debian/changelog
  * patterns: Terminate short pattern by ~ and ! (LP: #1911676)
  * Improve immediate configuration handling (LP: #1871268)
    - Do not immediately configure m-a: same packages in lockstep
    - Ignore failures from immediate configuration. This does not change the
      actual installation ordering - we never passed the return code to the
      caller and installation went underway anyway if it could be ordered at a
      later stage, this just removes spurious after-the-fact errors.

  [ JCGoran ]
  * Fix "extended_states" typo in apt-mark(8) (Closes: #969086)

apt (2.0.3) focal; urgency=medium

  [ Frans Spiesschaert ]
  * Dutch manpages translation update (Closes: #956313)

  [ David Kalnischkies ]
  * Add correct std namespace to nullptr_t

  [ Julian Andres Klode ]
  * Reinstate * wildcards (Closes: #953531) (LP: #1872200)
  * apt list: Fix behavior of regex vs fnmatch vs wildcards
  * debian/gbp.conf: We're in the 2.0.y branch
  * CI: Test on ubuntu:focal, not debian:unstable

 -- Julian Andres Klode <email address hidden> Thu, 14 Jan 2021 12:49:00 +0100

[noureddine ech-chouky (nourech)]

I'im using ubuntu image ,booted to usb using rufus

[rew (r-e-wolff)]

Guys..... What I don't get is that it is 2021 now, this bug has been reported (in 2019) and is tagged "fixed" and still the installer "crashed" and tells me it is this bug that is happening.....

This happens to me on a "clean" machine. I unplugged my harddisk, only have an SSD installed now. The installer image I downloaded yesterday (jan 23 2021).

[John Chittum (jchittum)]

reinstall attempted today. CD image downloaded on 20210124 and USB created via Rufus on Windows. Attempted install, indicated Install Third-Party Drivers. Crashed at the very end, after updating packages. hardware is a System 76 Gazelle (2019).

[Jerry May (qd0t)]

Install attempted today. CD image downloaded on 2021-01-23 and USB created via Rufus on Windows. Attempted install, indicated Install Third-Party Drivers. Crashed at the very end, after updating packages.

System is HP Omen 17-cb0070nr video=nVidia GeForce RTX2060
SecureBoot is OFF LegacyBoot is NOT enabled

But works just fine on HP Probook 6460b.
Next step: try with InstallThirdPartyDrivers DISABLED.

[Steve Langasek (vorlon)]

On January 24, 2021 12:12:19 AM PST, rew <email address hidden> wrote:
>Guys..... What I don't get is that it is 2021 now, this bug has been
>reported (in 2019)

It was not reported in 2019, it was reported in 2020.

The bug did not affect Ubuntu 20.04 at GA release time. The bug was noticed and escalated only once there was an SRU of glibc in focal-updates newer than what was on the release media, and took time to fix in apt.

There has not yet been a point release of focal with this fixed version of apt. It will be included in 20.04.2 which will be released in 2 weeks.

> and is tagged "fixed" and still the installer
>"crashed" and tells me it is this bug that is happening.....

It is marked fixed in apt. It is not marked fixed in ubuntu-cdimage.

The bug is fixed in daily images of focal, but these are not recommended for general use as they have the -proposed pocket enabled which is not the case for release images.

[B. C. Schmerker (bcschmerker)]

I confirm this problem still active in the latest Release ISO images for 20.04.1-LTS. Obviously a regression consistent with the ~vorlon observation(s) -- didn't happen in 19.04 or 19.10. Involves PluginInstall.py failing to find exact versions of several packages, although I's unable to screen-shot prior to Installer terminating. Even with the ~qd0t workaround, openlp crashes on open, which didn't happen on 18.04.4-LTS.

Attempted clean install on four partitions: /boot (ext2), 4 GiB swap, /home (ext4), / (ext4)
emachines/acer EL1210-09 (Acer DA078L)
Advance Micro Devices Athlon 64 LE-1620 (P/N AD1620IAA5DH)
nVIDIA nForce 780a MCP (C77 64-bit geForce GPU in northbridge)
msi GT610-1GD3-LP (nVIDIA GF119 64-bit GPU, 1 GiB DDR3 VRAM)

[Anton (anton7)]

Until the new images are available:
Just update apt of the live system before installing and the installation should work.

For those who don't know how to:
Start Live-System/ISO-Image with internet connected
Choose "Try Ubuntu"
Open "Terminal"
Type:
 sudo apt-get update
 sudo apt-get install apt
Then start installation of Ubuntu with your favourite options - even with third party drivers.

[Ralph Houston (ralphjfh)]

Also have an NVidia graphics card and opted for 3rd party drivers. Will now try again without them.

[Ralph Houston (ralphjfh)]

Very superficial report, but methodical.
Installed and booted OK this time, from install as similar as possible to process that encountered bug.
Differences:
1. Installed from livedisk Ubuntu still running after install failure, rather than direct from boot.
2. Did not create partitions, but reformatted (same) destination.
3. Did not ask for proprietary third party drivers.
So suspect the issuse is indeed in the the drivers and probably the NVidia one, from past experience.

[B. C. Schmerker (bcschmerker)]

No longer affects openlp 2.4.0 and 2.4.6, which OpenLP at GitLab has declared a WontFix. Awaiting 2.9.1 (unreleased as of 29 January 2021) for focal-proposed, groovy-proposed, and hirsute-proposed. I's able to get the EL1210-09 fully up by cherrypicking packages appropriate for nVIDIA 390.nn from the focal Repository, post-installation with nouveau.

[Alf HP Lund (alf-c)]

Confirming bug as of today on HP ZBook 15 G3 with NVIDIA M2000M with disk image downloaded yesterday from ubuntustudio.org https://cdimage.ubuntu.com/ubuntustudio/releases/20.04.1/release/ubuntustudio-20.04.1-dvd-amd64.iso.torrent

[Alf HP Lund (alf-c)]

Even though the installer crashed, powering off the machine and restarting sent me to a 'Perform MOK management' menu where I had to input my chosen password from the relevant step in the installation process. After that rebooting took me to the Grub menu and I could successfully start Ubuntu Studio.

After login there was a short flickering on the screen which I suspect could be the NVIDIA driver failing and falling back to the intel HD Graphics 530.

[Leon Pappas (nephilim9)]

I went along withe the whole mokutil route to get the NVidia drivers to
work but that failed to rectify the problem.

The GUI started having huge issues (Second monitor stopped working. GUI
would freeze and need a reboot). Tried reverting back to Nouveau and in
the process lost my server.. Gui stopped working completely.

Luckily I could still access the drive contents. and installed on a new
drive. Still not working 100% Second screen is detected but does not
work. I get a black screen with a white mouse pointer. I can drag a
window onto the monitor but if I release it it's gone. (I can't see
where it is to drag it back)

On 2021/02/04 20:37, Alf Haakon Lund wrote:
> Even though the installer crashed, powering off the machine and
> restarting sent me to a 'Perform MOK management' menu where I had to
> input my chosen password from the relevant step in the installation
> process. After that rebooting took me to the Grub menu and I could
> successfully start Ubuntu Studio.
>
> After login there was a short flickering on the screen which I suspect
> could be the NVIDIA driver failing and falling back to the intel HD
> Graphics 530.
>

[rgonnering (roger-gonnering)]

I have a new HP Envy TE-01 with Windows. Tried to load Ubuntu Studio 20.04 to dual boot. Installation crashed.

[Sebcio7 (sebcia7)]

Installation of version 20.10 crashed on Acer Aspire V Nitro

[Magnus Falk (jamfalk)]

Hello,
The installer crashed during installation of Jamulus OS on my Seagate BarraCuda 510 M2 SSD from USB live image. The bug was already reported (3rd party drivers) but I have some extra hardware info in attached JamulusOS.txt-file if needed.
Thanks for an excellent work!
Yours Magnus Falk in Oslo, Norway

[dragonhahney (dragonhahney)]

Thank you, sir/madam.

On Wed, Mar 10, 2021, 6:56 AM Sancho <email address hidden> wrote:

> ** Changed in: apt (Ubuntu Bionic)
> Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are subscribed to apt in
> Ubuntu.
> Matching subscriptions: dragonhahney
> https://bugs.launchpad.net/bugs/1871268
>
> Title:
> Installation fails due to useless immediate configuration error when
> "Install Third-Party Drivers" is selected
>
> Status in Ubuntu CD Images:
> Fix Released
> Status in apt package in Ubuntu:
> Fix Released
> Status in apt source package in Bionic:
> Fix Released
> Status in apt source package in Focal:
> Fix Released
> Status in apt source package in Groovy:
> Fix Released
> Status in apt package in Debian:
> Fix Released
>
> Bug description:
> [Impact]
> Installations that really succeeded would then fail because APT could
> not immediately configure a package. Which is a pointless way to fail at
> that point, because everything did work out anyway.
>
> We have two changes that help address this:
>
> * The first one stops immediately configuring multi-arch siblings
> (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
> necessary, and caused all the libc6:i386 failures here.
>
> * The second change sort of also supersedes the first one: It just
> ignores any errors from immediate configuration, relying on the fact
> that it's checked and rectified at a later point if there are
> unconfigured packages (which is what made all those failures happen
> spuriously after having successfully installed everything).
>
> [Test case]
> We have one test case in EIPP format in the Debian bug 973305 which was
> only helped by the second change, not the first one. Run
> /usr/lib/apt/planners < eipp.log and check there are no errors.
>
> TODO: It's unclear if the APT from proposed installed in the live
> session will fix the installer, needs investigation, but would make a
> useful test case.
>
> [Regression potential]
> It's imaginable that we missed something somewhere and some path that
> checked for a set error doesn't check it anymore, and we report success
> when we hit an error, but it seems unlikely.
>
> Behavior of --simulate changes. This used to fail before as well, and
> will now only produce a warning. We don't believe that is a reason of
> concern.
>
> [Groovy SRU]
> The groovy SRU is a sync of the 2.1.11 micro release from Debian
> unstable which also incorporates changes to the documentation: A typo fix,
> replacing focal with groovy in examples, and minor Dutch manual pages
> translation updates.
>
> We do not have test cases for the documentation changes, and we do not
> consider there to be a huge regression potential. As long as they
> build, they should be readable - maybe some words are wrong in the
> translation, who knows.
>
> [Original bug report]
> Test Case
> 1. Install Ubuntu Desktop on hardware with an nVidia card and select to
> install 3rd party drivers
> 2. Proceed with installation
>
> The following error message is displayed in /var/log/syslog
> /plugininstall.py: Verif...

[Julian Andres Klode (juliank)]

Corrected the task for bionic as per policy (in progress means SRU uploaded).

I'll be working on the bionic SRU tomorrow, I've just prepared SRUs for groovy and focal for other issues, and will be cherry-picking these patches on top of those :)

[Łukasz Zemczak (sil2100)]

Hello andresgenovez, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.13 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

[Pedro Principeza (pprincipeza)]

Hi. Input from a customer:

[ . . . ]
I just tested a "do-release-upgrade" from bionic to focal and did not get any errors.

I installed 18.04, installed the nvidia-driver-418 and enabled i386 arch. I then enable the
bionic-proposed repo and did an update/dist-upgrade, rebooted, and did a do-release-upgrade with no errors.
[ . . . ]

Changing tags. Thanks!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted apt (1.6.13) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.9-0ubuntu7.23 (amd64, i386)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[[e-mail] (kevindorseymackall1)]

can u fix

[Jaime Antonio (jaisuav)]

no me instala version 20.10

[Launchpad Janitor (janitor)]

This bug was fixed in the package apt - 1.6.13

---------------
apt (1.6.13) bionic; urgency=medium

  [ David Kalnischkies ]
  * Fix incorrect base64 encoding due to int promotion (LP: #1916050)
  * Harden test for no new acquires after transaction abort (Closes: #984966)
    (LP: #1918920)

  [ Julian Andres Klode ]
  * Implement update --error-on=any (Closes: #594813) (LP: #1693900)
  * Include all translations when building the cache (LP: #1907850)
  * Add basic support for the Protected field
  * Do not require force-loopbreak on Important packages
    (Closes: #983014) (LP: #1916725)
  * Protect currently running kernel at run-time (LP: #1615381)
  * Make ADDARG{,C}() macros expand to single statements
  * Improve immediate configuration handling (LP: #1871268)
    - Do not immediately configure m-a: same packages in lockstep
    - Ignore failures from immediate configuration. This does not change the
      actual installation ordering - we never passed the return code to the
      caller and installation went underway anyway if it could be ordered at a
      later stage, this just removes spurious after-the-fact errors.
      (Closes: #973305, #188161, #211075, #649588)
  * Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566)
    (LP: #1918907)

  [ Balint Reczey ]
  * Set LC_ALL=C.UTF-8 for unattended-upgrades environment when parsing its --help
    (LP: #1806076)

 -- Julian Andres Klode <email address hidden> Fri, 12 Mar 2021 14:09:15 +0100

[Becourt G (befou)]

Hello
I was using ubuntu 20.04 ( update XXXX.53 running )
prior to this re_installation of ubuntu, starts of ubuntu were not stable, since release xxxx.48
"boot fail description"was the message I pay attention to.
most of the time reconfig of grub seemed to take care of the problem, still every ether day the start failed again and again.
so I decided to reinstall and i got stuck during the install progress.
As for now I will try the 'groovy' solution and/or the "no third party install " option.
this message to just to let you know.
thanks

[Diego de Castro Barcellos (diegocb81)]

Good day!

Thank you very much for the support, i'll try to fix it.

Best wishes,

Diego Barcellos

Em qui., 1 de jul. de 2021 às 00:25, metin bağdat <
<email address hidden>> escreveu:

> ** Changed in: apt (Ubuntu)
> Assignee: (unassigned) => metin bağdat (metinbagdat)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871268
>
> Title:
> Installation fails due to useless immediate configuration error when
> "Install Third-Party Drivers" is selected
>
> Status in Ubuntu CD Images:
> Fix Released
> Status in apt package in Ubuntu:
> Fix Released
> Status in apt source package in Bionic:
> Fix Released
> Status in apt source package in Focal:
> Fix Released
> Status in apt source package in Groovy:
> Fix Released
> Status in apt package in Debian:
> Fix Released
>
> Bug description:
> [Impact]
> Installations that really succeeded would then fail because APT could
> not immediately configure a package. Which is a pointless way to fail at
> that point, because everything did work out anyway.
>
> We have two changes that help address this:
>
> * The first one stops immediately configuring multi-arch siblings
> (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
> necessary, and caused all the libc6:i386 failures here.
>
> * The second change sort of also supersedes the first one: It just
> ignores any errors from immediate configuration, relying on the fact
> that it's checked and rectified at a later point if there are
> unconfigured packages (which is what made all those failures happen
> spuriously after having successfully installed everything).
>
> [Test case]
> We have one test case in EIPP format in the Debian bug 973305 which was
> only helped by the second change, not the first one. Run
> /usr/lib/apt/planners < eipp.log and check there are no errors.
>
> TODO: It's unclear if the APT from proposed installed in the live
> session will fix the installer, needs investigation, but would make a
> useful test case.
>
> [Regression potential]
> It's imaginable that we missed something somewhere and some path that
> checked for a set error doesn't check it anymore, and we report success
> when we hit an error, but it seems unlikely.
>
> Behavior of --simulate changes. This used to fail before as well, and
> will now only produce a warning. We don't believe that is a reason of
> concern.
>
> [Groovy SRU]
> The groovy SRU is a sync of the 2.1.11 micro release from Debian
> unstable which also incorporates changes to the documentation: A typo fix,
> replacing focal with groovy in examples, and minor Dutch manual pages
> translation updates.
>
> We do not have test cases for the documentation changes, and we do not
> consider there to be a huge regression potential. As long as they
> build, they should be readable - maybe some words are wrong in the
> translation, who knows.
>
> [Original bug report]
> Test Case
> 1. Install Ubuntu Desktop on hardware with an nVidia card and select to
> install 3rd party drivers
> 2. Proceed with installation
>
> The following error mess...

[Ministerio Profetico Sal e Luz (mpsl)]

erro no final da instalação via pen drive.

[Douglas Purdy (douglas150)]

This was a reinstall after Ubuntu 20.04 boot crashes after a recent update. The same install options were selected for this reinstall. Ubuntu had worked for months but after an update a month n or so ago it always crashed at boot between the ubuntu logo and rotating circle's shutoff and the login screen. This did not appear to have any relation to the Invidia card boot fixes on the web. The disk has 3 areas rated prefail like my other Ubuntu computer which has no problems.

[Rainer Bernhardt (rrber)]

Updating NVIDIA driver from 460 to 470 messed up my system (even GRUB). Making an parallel install brought GRUB back to life, but I was not able to fix it. Even starting from pen drive only worked when using safe grafic after the NVIDIA update. System is working since years (16.04, 18.04, 20.04). So I decided to completely wipe the ssd and to reinstall. Then the installer ran into this error. I assume NVIDIA also touches the cards firmware when updating the driver.