Hello, Steve.  Thank you for looking into this for me.

I was attempting to replace Ubuntu 13.10 with 20.04. After downloading the
.iso file and Rufus onto my Win7 machine,  I created a bootable thumb drive
that passed verification.
During the install process, I selected the OEM install.  Everything seemed
to be going well.  The GUI cam up with its red background and wire frame
kitty cat and it seemed like it was near the end of the process. As I was
answering some questions... user name, etc.  I was halted by a big white
pop-up that said:

"We're sorry, the installer crashed...."

The message went on to explain that the problem would be reported and I
would have a chance to add any comments. I closed that pop-up and the
install seemed like it was wrapping up the installation when I was
bombarded with a sequence of other pop-ups, the first one stating that:

"The problem cannot be reported"

followed by several others, each stating:

"Sorry, Ubuntu 20.04 has experienced an internal error."

and one that said:

"The application IBUS Preference has closed unexpectedly"

Ultimately, I was given one last message stating that if the problem didn't
go away, reboot.  At that point, the thing -appeared- to be working, but I
didn't try to do anything and opted to reboot.  It never came back from
that.  Now, all get is a crash on start that takes me back to whatever line
command system it there... grub gnu something 2.0-19.  I don't speak GNU,
so I'm DIW right there.

Additionally, I have tried to reinstall 20.04, but after I select type of
install, it just crashes down to the command line again and won't even try
to install or tell my why.  At the moment, I'm thinking that there is
something in the 13.10 stuff that it making the 20.04 stuff have
heartburn.  If that is the case, I'm wondering if just reformatting the C
drive will fix it.

I have photos of most of the screen pop-ups that occurred,. so if you think
that seeing them and reading the (to me) gibberish on them would help
analyze the problem, let me know and I will forward them.


Thanks for any help.
Dave


On Sat, Apr 25, 2020 at 1:00 PM Steve Langasek <email address hidden>
wrote:

> > System crashed
>
> Can you explain exactly what you saw?  The ubiquity logs attached to
> your bug report don't show a crash.
>
> > can only access line command labeld GRUB GNU 2.0-19
>
> Which seems to be the version of grub from saucy (Ubuntu 13.10).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874965
>
> Title:
>   install 20.04 crashed
>
> Status in ubiquity package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Replacing Ubuntu 13.10 with 20.04.  No dual boot, no partition, just
>   erase 13.10 and install 20.04.  System crashed, can only access line
>   command labeld GRUB GNU 2.0-19
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: ubiquity 20.04.15
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CasperVersion: 1.445
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr 24 21:02:17 2020
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset ---
>   LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
>   ProcEnviron:
>    LANGUAGE=en_US.UTF-8
>    PATH=(custom, no user)
>    XDG_RUNTIME_DIR=<set>
>    LANG=en_US.UTF-8
>    LC_NUMERIC=C.UTF-8
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1874965/+subscriptions
>