[Bug 1926672] Re: ubiquity-gtk installer crashes in focal 20.04.02 after partitioning due to existing EFI partition

Fri May 21 01:09:13 UTC 2021

** Attachment added: "apport.ubiquity.mzexll29.apport"
   https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+attachment/5499132/+files/apport.ubiquity.mzexll29.apport

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1926672

Title:
  ubiquity-gtk installer crashes in focal 20.04.02 after partitioning
  due to existing EFI partition

Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  In focal 20.04.02 the ubiquity-gtk installer (20.04.15.11/focal-
  updates) always crashes after the partition step.

  Although this seems to be an old bug, I could not find a relevant bug
  report so far.

  I am having this issue when installing Ubuntu 20.04 to removable media
  from an existing Ubuntu 20.04 system. I could reproduce the issue on a
  PC in UEFI mode and on another one in BIOS mode. Before reporting this
  bug, I tested the installer on both Live USB media and internal disks.

  How to reproduce?

  1. The install medium needs to be writable (i.e. no CD/DVD) and contain a mounted EFI partition (e.g. /dev/sda1), while the target presumably needs to be a removable medium or a secondary disk.
  2. sudo --preserve-env=DBUS_SESSION_BUS_ADDRESS,XDG_RUNTIME_DIR sh -c 'ubiquity gtk_ui'
  3. In the ubiquity installer create a GPT partition on the target medium (e.g. /dev/sdb) containing an EFI partition (e.g. /dev/sdb1) and a root partition (e.g. /dev/sdb2), and set the Grub target ("boot disk") accordingly.
  4. The installer will ask for confirmation, stating that the partition table of both disks will change and that the two newly created partitions will be formatted. In case of an existing swap partition on the primary disk, this partition will also be formatted (which I consider another bug).
  5. After the crash, you can notice that
     a. the new system has been partially installed, as /target (e.g. /dev/sdb2) is mounted and contains 329 MB
     b. the EFI partition of the install medium or primary disk (e.g. /dev/sda1) has been unmounted from /boot/efi and remounted to /target/boot/efi
     c. the target EFI partition (e.g. /dev/sdb1) has been created and formatted, but is unmounted and empty.

  $ cat /target/etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # <file system> <mount point>   <type>  <options>       <dump>  <pass>
  # / was on /dev/sdb2 during installation
  UUID=76ecfd0f-dae5-4801-9db0-7d8bc8d20b8f /               ext4    errors=remount-ro 0       1
  # /boot/efi was on /dev/sda1 during installation
  UUID=A815-6B37  /boot/efi       vfat    umask=0077      0       1
  # swap was on /dev/sda6 during installation
  UUID=c2e0cb67-23de-4ab3-be19-4123e6229ade none            swap    sw              0       0

  $ sudo du -shx /target/* | sort -h
  4,0K    /target/home
  4,0K    /target/lib64
  4,0K    /target/media
  4,0K    /target/mnt
  4,0K    /target/opt
  4,0K    /target/proc
  4,0K    /target/srv
  4,0K    /target/sys
  4,0K    /target/tmp
  4,0K    /target/writable
  12K     /target/dev
  12K     /target/root
  16K     /target/lost+found
  16K     /target/meta
  84K     /target/snap
  96K     /target/run
  3,8M    /target/etc
  4,1M    /target/boot
  9,7M    /target/sbin
  9,8M    /target/var
  14M     /target/bin
  48M     /target/lib
  240M    /target/usr

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.15.11
  ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 30 00:34:13 2021
  InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz root=UUID=E6BD-0CD8 file=/cdrom/preseed/ubuntu.seed maybe-ubiquity debian-installer/language=de keyboard-configuration/layoutcode=de iso-scan/filename=/ubuntu-18.10-desktop-amd64.iso boot=casper persistent noprompt quiet splash --
  InstallationDate: Installed on 2018-12-11 (870 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to focal on 2020-10-26 (185 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=d58bb821-fce1-4730-802d-4afdcf512495 ro quiet splash vt.handoff=7
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubiquity 21.04.19
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute wayland-session oem-config
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926672/+subscriptions