Error when installing Kubunt 22.04

[masterok]

Good day.
An error occurred while installing Kubunt 22.04.
Boot from a flash drive. I divide SSD into 3 sections: 500 MB - EFI (fat32), 16 GB - swap, other - / (btrfs) I run the installer, specify the full version with additional drivers, mark the partitions, then select the time zone and at this point, after a few seconds, a window appears that an error occurred and you need to send a report. However, the report window is empty and there is only a close button. I close the error window and the system installation is interrupted. (Ubuntu Mate, Ubuntu 22.04 and Manjaro do not have this problem.) I need advice on how to solve the insertion problem.
Thanks for the help.

[jlittle]

You might find out more if you run the installer in a konsole:

Open a konsole and

ubiquity

However, IME that does give more info, but mostly it's a Python back trace and doesn't much help, though there can be something google finds.

I'd check the installer checksums, either the original iso or on the USB.

[masterok]

I downloaded the Kubuntu image twice on the official website and recorded it with a standard utility. If you run "ubiquity" through the terminal, it does not show anything if you make a mistake.

[masterok]

With the help of "ubuntu-bug ubiquity" managed to extract the error report and create a bug for the launchpad.
https://bugs.launchpad.net/ubuntu/+s...y/+bug/1971957

May 6 08:09:30 kubuntu ubiquity[5328]: Starting the installation
May 6 08:09:30 kubuntu ubiquity[5328]: debconffilter_done: ubi-timezone (current: ubi-timezone)
May 6 08:09:30 kubuntu ubiquity[5328]: Step_before = page
May 6 08:09:30 kubuntu ubiquity[5328]: switched to page Form
May 6 08:09:30 kubuntu ubiquity: Traceback (most recent call last):
May 6 08:09:30 kubuntu ubiquity: File "/usr/share/ubiquity/install.py", line 769, in <module>
May 6 08:09:30 kubuntu ubiquity: install = Install()
May 6 08:09:30 kubuntu ubiquity: File "/usr/share/ubiquity/install.py", line 69, in __init__
May 6 08:09:30 kubuntu ubiquity: assert os.path.ismount(self.target), \
May 6 08:09:30 kubuntu ubiquity: AssertionError: Failed to mount the target: /target
May 6 08:09:30 kubuntu systemd[1]: Started crash report submission.
May 6 08:09:30 kubuntu whoopsie[14390]: [11:09:30] Using lock path: /var/lock/whoopsie/lock

[claydoh]

recorded it with a standard utility

I usually suggest trying a different utility, as these can sometimes create faulty disks.
I normally use dd on the command line, but I also use Etcher, which for me has never made a bad disk.

[masterok]

I usually suggest trying a different utility, as these can sometimes create faulty disks.
I normally use dd on the command line, but I also use Etcher, which for me has never made a bad disk.

I used Etcher. The result is the same: an error after manually dividing the SSD into sections.

[Snowhog]

IF you are using the booted USB (Live Kubuntu) to do the partitioning of the destination disc, that (unfortunately) has almost always been problematic. It's one of the few 'unresolved' issues with Kubuntu IMO.

You are better off partitioning the destination disc before booting into the Live Kubuntu and running the installation. I (and many others) use Gparted for this.

[masterok]

IF you are using the booted USB (Live Kubuntu) to do the partitioning of the destination disc, that (unfortunately) has almost always been problematic. It's one of the few 'unresolved' issues with Kubuntu IMO.

You are better off partitioning the destination disc before booting into the Live Kubuntu and running the installation. I (and many others) use Gparted for this.

In the first message, I indicated that the disk is already divided into three partitions. It is not possible to skip the manual mode. There I still need to select the file system of the partition and check the format.
SSD was previously divided into three sections in Gparted. 500 MB - EFI (fat32), 16 GB - swap, other - / (btrfs)

[claydoh]

There I still need to select the file system of the partition and check the format.

You should not need to check the 'format' option on the partitions if you have set them up already.

[masterok]

The "format" check mark does not affect the result. It is also not affected by disconnecting the Internet during installation.

[jlittle]

Clutching at straws... I've had the installer crash when there's a previous installation in the @ subvolume, even if I intend it to be overwritten. I suggest having a look in the btrfs using dolphin, or maybe btrfs subvolume list.

[kernelbasher]

Are you trying to preserve data from a previous install at all?
If not. Just for my sanity I'd try either letting kub do what it wants or install gparted in the live session and repartition / btrfs to / ext4
Always make sure grub is pointing to the correct location, which in your case will be your efi part