Ubuntu installer crashed

[Sridhar Gollamudi]

I was trying to install Ubuntu on my new Dell XPS 15 laptop which came with Windows 10 Professional. I performed the following before the crash:

1. Created a bootable USB drive with Ubuntu
2. Disabled secure boot on Windows
3. Changed the storage controller protocol from RST to AHCI
4. Turned off BitLocker
5. Ran Ubuntu installer

Please let me know what went wrong and how I could get my computer to work as intended.

Thanks,
Sri

[Chris Guiver (guiverc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1900782

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

We have no details as to what release you tried, if a desktop, server or other release, what ISO was used, nor if you validated your ISO before writing to your installation media, or validated the write after written to installation media. I personally find the write to installation media the most in needing of check, but you've provided no details as to what checks you made (let alone what you tried to install).

I'm marking this bug incomplete, please change it to "New" once you've run the `apport-collect` step, though I suspect it's not a bug, but user procedure error.

Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

[Sridhar Gollamudi (sgollamudi)]

Hello Chris,

Thanks for your detailed response. It's interesting that you did not
receive any details regarding the installation failure, since the error
message that I got said that a bug report with all details about the
failure was being sent. At present I am not able to boot into Ubuntu; I
will try again, and if successful, run the diagnostic that you suggested.

Best,
Sri

On Tue, Oct 20, 2020 at 10:30 PM Chris Guiver <email address hidden>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please execute the following command only once, as it
> will automatically gather debugging information, in a terminal:
>
> apport-collect 1900782
>
> When reporting bugs in the future please use apport by using 'ubuntu-
> bug' and the name of the package affected. You can learn more about this
> functionality at https://wiki.ubuntu.com/ReportingBugs.
>
>
> We have no details as to what release you tried, if a desktop, server or
> other release, what ISO was used, nor if you validated your ISO before
> writing to your installation media, or validated the write after written to
> installation media. I personally find the write to installation media the
> most in needing of check, but you've provided no details as to what checks
> you made (let alone what you tried to install).
>
> I'm marking this bug incomplete, please change it to "New" once you've
> run the `apport-collect` step, though I suspect it's not a bug, but user
> procedure error.
>
> Bug reporting is mostly about finding & fixing problems thus preventing
> future users from hitting the same bug.
>
> I suspect a Support site would be more appropriate, eg.
> https://answers.launchpad.net/ubuntu. You can also find help with your
> problem in the support forum of your local Ubuntu community
> http://loco.ubuntu.com/ or asking at https://askubuntu.com or
> https://ubuntuforums.org, or for more support options please look at
> https://discourse.ubuntu.com/t/community-support/709
>
> ** Changed in: glibc (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1900782
>
> Title:
> Ubuntu installer crashed
>
> Status in glibc package in Ubuntu:
> Incomplete
>
> Bug description:
> I was trying to install Ubuntu on my new Dell XPS 15 laptop which came
> with Windows 10 Professional. I performed the following before the
> crash:
>
> 1. Created a bootable USB drive with Ubuntu
> 2. Disabled secure boot on Windows
> 3. Changed the storage controller protocol from RST to AHCI
> 4. Turned off BitLocker
> 5. Ran Ubuntu installer
>
> Please let me know what went wrong and how I could get my computer to
> work as intended.
>
> Thanks,
> Sri
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1900782/+subscriptions
>

[Sridhar Gollamudi (sgollamudi)]

Running "apport-collect 1900782" gave me the following result:
Package glibc not installed and no hook available, ignoring

[Sridhar Gollamudi (sgollamudi)]

I am able to log into the Ubuntu partition now. I am not sure if the installation error regarding glibc got fixed or if I should do something about it.

[Sridhar Gollamudi (sgollamudi)]

I guess it looks like glibc is correctly installed?

$ aptitude show libc6
Package: libc6
Version: 2.31-0ubuntu9.1
State: installed
Automatically installed: yes
Multi-Arch: same
Priority: required
Section: libs
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Uncompressed Size: 13.6 M
Depends: libgcc-s1, libcrypt1 (>= 1:4.4.10-10ubuntu4)
Recommends: libidn2-0 (>= 2.0.5~)
Suggests: glibc-doc, debconf | debconf-2.0, locales
Conflicts: openrc:i386 (< 0.27-2~)
Breaks: hurd:i386 (< 1:0.9.git20170910-1), hurd (< 1:0.9.git20170910-1), iraf-fitsutil:i386 (<
        2018.07.06-4), iraf-fitsutil (< 2018.07.06-4), libtirpc1:i386 (< 0.2.3), locales:i386 (<
        2.31), locales (< 2.31), locales-all:i386 (< 2.31), locales-all (< 2.31), nocache:i386 (<
        1.1-1~), nocache (< 1.1-1~), nscd:i386 (< 2.31), nscd (< 2.31), r-cran-later:i386 (<
        0.7.5+dfsg-2), r-cran-later (< 0.7.5+dfsg-2), wcc:i386 (< 0.0.2+dfsg-3), wcc (<
        0.0.2+dfsg-3), libc6:i386 (!= 2.31-0ubuntu9.1)
Replaces: libc6-amd64, libc6-amd64:i386, libc6-amd64:x32, libc6-amd64:x32-i386-cross,
          libc6-amd64:i386-x32-cross, libc6:i386 (< 2.31-0ubuntu9.1)
Description: GNU C Library: Shared libraries
 Contains the standard libraries that are used by nearly all programs on the system. This package
 includes shared versions of the standard C library and the standard math library, as well as many
 others.
Homepage: https://www.gnu.org/software/libc/libc.html

[Chris Guiver (guiverc)]

Currently little is known about your system.

I said "We have no details as to what release you tried, if a desktop, server or other release, what ISO was used, nor if you validated..."

Your last post indicates it's a focal (20.04) system, so thank you. However we still don't know your ISO used, if you're talking Server ISO (thus installer was `subiquity`), a desktop ISO (thus `ubiquity`) etc

Much of that detail is obtained using `apport-collect`, but with installer issues, those logs are essential (but until ISO is known, the package name currently can't be changed)

I'm changing this back to incomplete, as requested detail (namely details as to server/desktop) wasn't provided. Once I know that, I'll change package to reflect that & `apport-collect` should be more helpful.

(laptop implies desktop to me, but a lot of folks use laptops as low-powered severs so we can't make assumptions. Once I know it's server/desktop & ISO, I'll change package to `ubiquity` or whatever matches the ISO you used, and you can try `apport-collect` again).

Thank you for helping make Ubuntu better.

[Launchpad Janitor (janitor)]

[Expired for glibc (Ubuntu) because there has been no activity for 60 days.]