kaosx / calamares Goto Github PK

Submission type

• Bug report
• Feature Request

KaOS ISO date you are having issues with or have a request for

KaOS 2016.11

How did you create the Live Media?

Using Rufus on Windows 10

Did you check the md5sum of the downloaded ISO?

No

Describe the issue you encountered

Every time I try to install KaOS 2016.11 using Calamares installed at 19% I get this error message:

Boost.Python error in job "userkf5".
<class 'AttributeError'>
'NoneType' object has no attribute 'group'
Traceback:
File "/usr/lib/calamares/modules/userkf5/main.py", line 115, in run
print (m.group(0))

Steps to reproduce the problem

Happens every time I try to install

Include the installation.log:

• Live mode: ~/installation.log
• Installed System: /var/log/installation.log

installation.log.txt

With e-c-m from frameworks 5.6.0 the install paths are not honored correctly. Even-though project is set to install in /usr, with the libdir set to /usr/lib, part of the modules are installed in /usr/lib64, other parts in /usr/lib.
Downgrading to e-c-m 1.5.0, all installs correctly.

Calamares failed to copy files and the installation process is aborted showing errors.
To avoid such unwanted condition (1), fisrt i erase all partitions on my Hard Disk , (2) then reboot the system and (3) finally start fresh install.
Is there any fix ?

md5sum of my ISO is - 47c3e2f05dd02a4545b7d5e97d879f53

blkid --
/dev/sda1: UUID="12E3-F868" TYPE="vfat" PARTUUID="2d189d62-ac5f-4748-8ae7-e8cfb27572d3"
/dev/sda2: UUID="cf29b84f-c07c-4515-92f6-7e5b44475b31" TYPE="ext4" PARTUUID="ed7bcd19-71f0-4981-874c-24831bc48c2d"
/dev/sda3: UUID="56f010de-d79c-4602-a2de-79b52cb66cfe" TYPE="swap" PARTUUID="02e97669-5573-41db-8353-090b0b7b344d"
/dev/sdb1: LABEL="storage" UUID="9356b303-9538-4f78-a179-4c0dcc6048d9" TYPE="ext4" PARTUUID="3eefe9b0-3a86-4005-98f7-c9bdbccf2ac1"
/dev/sdc1: UUID="2016-06-22-20-27-56-00" LABEL="KAOS_20160622" TYPE="iso9660" PTUUID="3d6a0a9c" PTTYPE="dos" PARTUUID="3d6a0a9c-01"
/dev/sdc2: SEC_TYPE="msdos" LABEL="KAOS_EFI" UUID="AF6A-4229" TYPE="vfat" PARTUUID="3d6a0a9c-02"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"

Steps to reproduce

• As boot option I selected Start KaOS Live, which uses nouveau.
• Run Install KaOS from the live system
• In the installer's Licence tab, Nvidia's license agreement is a requirement to continue with the installation

Expected

• User shouldn't be forced to agree with Nvidia's license if non-free wasn't selected

I updated to the latest calamares and calamares-debug and when it comes to partition it just breaks down:

Fatal signal: Segmentation fault
----- Backtrace -----
0x4e9fab ???
0x5fa04e ???
0x5fa174 ???
0x7f07eb8b3aff ???
0x4be7a0 ???
0x55517e ???
0x6315fc ???
0x615fc5 ???
0x61460e ???
0x78e974 ???
0x7f07ec1fd6e8 ???
0x7f07ec23d7e3 ???
0x7f07ec23c28f ???
0x7f07ec23d34a ???
0x7f07ec23c28f ???
0x7f07ec23d34a ???
0x7f07ec23c28f ???
0x7f07ec23d34a ???
0x7f07ec23c28f ???
0x7f07ec2aefe1 ???
0x7f07ec2c4232 ???
0x7f07ec2c41c9 ???
0x7f07ec2c413c ???
0x7f07ec2c409b ???
0x7a1b49 ???
0x51b534 ???
0x87976e ???
0x5fa8df ???
0x8778da ???
0x522aa2 ???
0x51816a ???
0x6f1be4 ???
0x6f1c64 ???
0x6f3cc4 ???
0x6f453a ???
0x442ec4 ???
0x7f07eb89eb36 ???
0x7f07eb89ebf4 ???
0x44dc90 ???
0xffffffffffffffff ???

A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.

This is a bug, please report it. For instructions, see:
https://www.gnu.org/software/gdb/bugs/.

org.kde.drkonqi: Debugger process had an error QProcess::Crashed QList("gdb", "-nw", "-n", "-batch", "-x", "/tmp/drkonqi.YKiWlD", "-x", "/tmp/drkonqi.jTHfuj", "-p", "14082", "/usr/bin/calamares") QList("-nw", "-n", "-batch", "-x", "/tmp/drkonqi.YKiWlD", "-x", "/tmp/drkonqi.jTHfuj", "-p", "14082", "/usr/bin/calamares") QList("COLORTERM=truecolor", "DISPLAY=:1", "DRKONQI_APP_VERSION=3.3.2", "DRKONQI_SIGNAL=6", "DRKONQI_TMP_DIR=/tmp/drkonqi-uVzOBK", "DRKONQI_VERSION=5.93.0", "EDITOR=micro", "HISTCONTROL=ignoreboth", "HISTFILESIZE=10000", "HISTSIZE=10000", "HOME=/root", "KCRASH_AUTO_RESTARTED=1", "KDE_DEBUG=true", "KDE_FULL_SESSION=true", "KDE_SESSION_VERSION=6", "LANG=nl_NL.UTF-8", "LANGUAGE=", "LC_ALL=C.UTF-8", "LC_MESSAGES=nl_NL.UTF-8", "LOGNAME=root", "MAIL=/var/mail/root", "PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl", "PWD=/home/live/Downloads", "QT_IM_MODULE=qtvirtualkeyboard", "SHELL=/bin/bash", "SHLVL=1", "SUDO_COMMAND=/bin/su", "SUDO_GID=100", "SUDO_UID=1000", "SUDO_USER=live", "TERM=xterm-256color", "USER=root", "VISUAL=micro", "XAUTHORITY=/run/user/1000/xauth_kCiqkx", "XDG_CURRENT_DESKTOP=KDE", "_=/usr/bin/calamares")
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Calamares is already running.
Unable to start Dr. Konqi
Re-raising signal for core dump handling.

This is what I get when I come to the partition page. Furthermore, if installation succeeeds, oder versions of calamares hung on kf5-user module script, theres no way to boot it as it doesnt find root device (in my case the /dev/nvme0n1p3); the apple mini architecture is not secured booted and I tried to update grub via arch-install-scripts and arch-chroot, but it tells me to not have any space (chroot-environment). but BTT:

I gave gparted a chance and partitioned the whole stuff by hand; I wanted a btrfs encrypted file system and LUKS probably doesn't work with dracut. If once a pwd is given, it always asks for passwords, even if I repartitioning the ssd. This has to to with the zfs driven encryption: I tried refind (standard boot on my device), systemd or no bootloader but all the same stuff.

Yesterday I had a good KaoSx on my device but today it refused to boot. To arch-chroot is not a good idea, because you can't update the new system from squashfs because of the chroot environment:

The only starting option is to make grub2 on first EFI boot entry and with luck it will find the root device.

Submission type

• Bug report
• Feature Request

KaOS ISO date you are having issues with or have a request for

KaOS 2017.01 ISO

How did you create the Live Media?

Using rufus-2.11.exe on Windows 10

Did you check the md5sum of the downloaded ISO?

No

Describe the issue you encountered

Installation gets to the end and a error dialog pops up. Behind it text says the installation was successful and to reboot. Click Close on the dialog, reboot the system and it just sits at a black screen with flashing prompt.

Photos:
http://imgur.com/xvBEXoB

http://imgur.com/WuUVjeG

Machine is an Intel 3rd gen i5, z77 chipset based pc with 8gb ram and an OCZ TRION 100 SSD.

Steps to reproduce the problem

I've tried re-installing and get the same experience.

Include the installation.log:

• Live mode: ~/installation.log
• Installed System: /var/log/installation.log

No /var/log/installation.log file exists, just four directories: cups, journal, old and samba, and there's no files in those.

Submission type

• Feature Request
  => Put in the default package the wifi driver for broadcom wifi card in order to have internet at the installation for macbook air. Their is no RJ12 port on this type of thin PC.

KaOS ISO date you are having issues with or have a request for

december 2016 (just before the KaOS 2017.01 ISO)

How did you create the Live Media?

on a usbkey

Did you check the md5sum of the downloaded ISO?

no problem with the iso

Describe the issue you encountered

installation on my mac air that haven't any RJ12 cable port.
I need to by a usb adaptator to plug RJ 12 cable to have internet in order to install.... the wifi driver for the broadcom wifi

Steps to reproduce the problem

not a bug but a request.

Include the installation.log:

• Live mode: ~/installation.log
• Installed System: /var/log/installation.log

…

Submission type

• Bug report
• Feature Request

KaOS ISO date you are having issues with or have a request for

20170217

How did you create the Live Media?

GnomeBaker

Did you check the md5sum of the downloaded ISO?

yes

Describe the issue you encountered

After installing KaOS sucessfully with separate partitions for "/", "/usr", "/var" and "/home" the first start from hard disk drive failed with the following error message:

ERROR: Root device mounted successfully, but /sbin/init does not exist.

"/sbin" in KaOS (and Arch Linux) is a symlink to "/usr/bin" (btw: I hate this change). This means that unless /usr is mounted, /usr/sbin/init will not exist. The installer doesn't take care of this fact when creating the initial ramdisk.

The problem can be fixed by changing the hooks and modifying "/etc/fstab":

1. In "/etc/fstab" the partion "/usr" has to be mounted with a passno of 0.

For the users, who are not so familiar with linux: The passno (fsck order) is the last column in "/etc/fstab" in each row. Hence the corresponding line should look like

UUID=a304512f-e1ce-499e-920f-5c18cd53969d /usr ext4 defaults,noatime 0 0
...

2. In "/etc/mkinitcpio.conf" the HOOKS line has to be extended with "usr" and you have to make sure that "fsck" and "block" are in this list, too.

3. Rebuild the initial ramdisk by executing: mkinitcpio -p linux

Steps to reproduce the problem

Install KaOS with a separate partition for /usr

Include the installation.log:

Sorry, I don't have a log file.

Submission type

• Bug report

Info regarding which version of Calamares is used, which Distribution

KaOS 2018.06 with Calamares version 3.2.0-2

Provide information on how the disks are set up, in detail, with full logs of commands issued

Disk /dev/sda: 596.2 GiB, 640135028736 bytes, 1250263728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x1770ce68

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 2000094 1998047 975.6M ef EFI (FAT-12/16/32)
/dev/sda2 2002942 202000383 199997442 95.4G 5 Extended
/dev/sda3 1246263296 1250263039 3999744 1.9G 82 Linux swap / Solari
/dev/sda4 202000384 1246263295 1044262912 498G 83 Linux
/dev/sda5 2004990 202000383 199995394 95.4G 83 Linux

Partition 2 does not start on physical sector boundary.
Partition 5 does not start on physical sector boundary.
Partition table entries are not in disk order.

What do you expect to have happen when Calamares installs?

KaOS 2018.06 installs properly

Describe the issue you encountered

La instalación ha fallado

Error de Boost.Python en la tarea "bootldr".
<class 'FileNotFoundError'>
[Errno 2] No such file or directory: '/tmp/calamares-root-nv2qvwd3/boot/loader/entries/KaOS_2018.06.conf'

Traceback:
File "/usr/lib/calamares/modules/bootldr/main.py", line 222, in run
install_bootloader(boot_loader, fw_type)

File "/usr/lib/calamares/modules/bootldr/main.py", line 203, in install_bootloader
create_conf(uuid, conf_path)

File "/usr/lib/calamares/modules/bootldr/main.py", line 97, in create_conf
with open(conf_path, 'w') as f:

Steps to reproduce the problem

When installed with squid, just after the installer is creating the user, throws this problem and can not follow the installation procedure

Include the installation.log (usually ~/Calamares/Calamares/Calamares.log, of the user Calamares runs as):

https://github.com/mikethewolf83/mikethewolf83.github.io/blob/master/calamares.log

Submission type

• Bug report

Info regarding which version of Calamares is used, which Distribution

KaOS 2018.04

Provide information on how the disks are set up, in detail, with full logs of commands issued

Went with the "erase disk"-option. Made no changes to anything.

• blkid: https://pastebin.com/ZBwShuUE
• fdisk -l: https://pastebin.com/0f4vMgWd

What do you expect to have happen when Calamares installs?

That it works?

Describe the issue you encountered

Error in Boost.Python job bootldr: https://drive.google.com/file/d/1byQNBKtiw08_sLNzyXplf3unLXQ1n17n/view?usp=sharing

Steps to reproduce the problem

Try to install KaOS 2018.04 in VMware Player (newest) with standard settings for "other linux 4.x or later kernel 64-bit" settings

Include the installation.log (usually ~/Calamares/Calamares/Calamares.log, of the user Calamares runs as):

https://pastebin.com/Ac80CBw7

I wanted to post this in the KaOS forums but the login doesn't work in Chrome and Firefox...

I found multiple Boost.Python job bootldr bugs by googling but these always talk about certain partition setups while I didn't change anything from the default settings. In the VMware Player I just changed the RAM to 10.088 GB and the CD to the ISO (sha256 is correct). I just chose to erase the drive in Calamares.
When I go into Octopi and click on SysInfo I just get a blank window: https://drive.google.com/file/d/1qi5gGRHK9HbsE4cS248kVSXCcUj9ojZ3/view?usp=sharing
When I shut down after the failed installation there are a few "warnings": https://drive.google.com/file/d/1sxKCeVdSc78oCaDmFZDxPrYErpkHUaPV/view?usp=sharing

Describe the bug
I'm on a 64-bit laptop (Thinkpad X201), BIOS only. I tried to install KaOS from the January USB, but kept failing to install (grub-install saying "unknown filesystem") or boot (drops into Grub rescue due to "unknown filesystem"). It finally worked when the root filesystem was changed from XFS to EXT4.

Screenshots and Logs
I'm sorry... I didn't save the logs and now it's working (on EXT4). I just wanted to report in case this is useful.

Thank you!

Submission type

• [ x] Bug report

Info regarding which version of Calamares is used, which Distribution

3.1.104

Provide information on how the disks are set up, in detail, with full logs of commands issued

installation.log https://pastebin.com/tFAMEmwE

blkid: https://pastebin.com/raw/ULGvLSzj
fdisk -l https://pastebin.com/XPs4atTZ

SysInfo: https://ptpb.pw/idrB

Version and environment

• KaOS-2019.09-x86_64.iso
• calamares 3.2.13.20190904-git-master-488ee03
• octopi-sysinfo-1129199776.log

Describe the bug
Installation on LVM partition fails with the message "The installer failed to format partition /dev/VG/pv2_root on disk 'VG'."

To Reproduce

1. Install KaOS under the condition,

• / on LV
• /usr on LV
• /var on LV

Expected behavior
System installed

Screenshots and Logs

• installation.log
  

Related case and discussion
As in the log, calamares deactivates the LVM partitions before formatting even if they are used as install partition, maybe this is the cause.

22:50:37 [6]: ClearMountsJob finished. Here's what was done:
"Successfully closed mapper device /dev/mapper/VG-LFS.\nSuccessfully closed mapper device /dev/mapper/VG-pv2_home.\nSuccessfully closed mapper device /dev/mapper/VG-pv2_root.\nSuccessfully closed mapper device /dev/mapper/VG-pv2_usr.\nSuccessfully closed mapper device /dev/mapper/VG-pv2_var.\nSuccessfully closed mapper device /dev/mapper/VG-v_home.\nSuccessfully closed mapper device /dev/mapper/VG-v_root.\nSuccessfully closed mapper device /dev/mapper/VG-v_usr.\nSuccessfully closed mapper device /dev/mapper/VG-v_var.\nSuccessfully disabled volume group VG."

LVM status after calamares crash.

  LifeBook10.lan  live  ~  sudo lvscan
  inactive          '/dev/VG/v_root' [8.00 GiB] inherit
  inactive          '/dev/VG/v_usr' [40.00 GiB] inherit
  inactive          '/dev/VG/v_var' [5.00 GiB] inherit
  inactive          '/dev/VG/v_home' [42.00 GiB] inherit
  inactive          '/dev/VG/LFS' [15.00 GiB] inherit
  inactive          '/dev/VG/pv2_usr' [10.00 GiB] inherit
  inactive          '/dev/VG/pv2_var' [10.00 GiB] inherit
  inactive          '/dev/VG/pv2_home' [13.00 GiB] inherit
  inactive          '/dev/VG/pv2_root' [5.00 GiB] inherit

Below is the same case of Manjaro maybe.
https://forum.manjaro.org/t/problem-installing-manjaro-18-0-4-using-calamares-in-a-lvm-environment/87501
In that thread, the latest version of calamares solves the problem(?).
Actually, the version of calamares on Manjaro is new (calamares 3.2.15-2).

Submission type

• [x ] Bug report
• Feature Request

KaOS ISO date you are having issues with or have a request for

20170217

How did you create the Live Media?

GnomeBaker

Did you check the md5sum of the downloaded ISO?

yes

Describe the issue you encountered

After booting from dvd the start of the live system failed. A timeout occurred while waiting for device /dev/disk/by-label/KAOS_20170217. The dvd has the correct label.

I took a look at the file system and there wasn't a directory "/dev/disk/by-label/". I was able to fix the problem by entering the following commands:

1. mkdir /dev/disk/by-label/

2. ln -s /dev/sr0 /dev/disk/by-label/KAOS_20170217

3. exit (Shell)

My system is a Levono ThinkCentre M55 PC with Intel Core 2 (Socket LGA775). Hard disk drive and DVD have an SATA bus type.

Steps to reproduce the problem

Just try to install KaOS from the iso image on the system mentioned above with an empty hard disk drive.

Include the installation.log:

Sorry, I don't have a log file.

I cannot install KAOS on my system. I tried running it from CD and USB, both the current version and the august 2015 version. On all occasions the live CD loads and next the screen freezes. The august 2015 version shows an error dialog: "KCMinit closed unexpectedly". At that point I can only reboot my computer... No problems in a VirtualBox.

A screenshot of the KaOS is available on Calamares website but unfortunately has major typos with RTL languages.

Resource: https://github.com/KaOSx/calamares/blob/master/src/branding/kaos_branding/languages.png

a. The Hebrew word for Hello is שלום (Shalom), not םולש. As it is written top-down, it is expected to read by turning the head to the left, not to the right as with LTR languages such as English.
b. There is a Yiddish translation for Hello as העלא in Google Translate (the screenshot has אלעה), but I suspect it is not widely used by Yiddish speakers.
c. Arabic word سلام (Salam) is reversed as well.
d. Unrecognized parse above Yiddish. Is it Persian? @yarons can you recognize it?

(Same issue reported on upstream as well calamares#1751)

I have chosen russian language while installation occurs, but I coudn't login after installation because my login was in English and default language was russian and I coudn't add another language. So in this case I reinstalled KAOS with default English language.

Submission type

• Bug report
• Feature Request

KaOS ISO date you are having issues with or have a request for

16.11

How did you create the Live Media?

Just used the ISO in VirtualBox

Did you check the md5sum of the downloaded ISO?

Yes:

➜  Downloads md5sum KaOS-2016.11-x86_64.iso 
0f77dd6f579a1f1f62731fed16d14062  KaOS-2016.11-x86_64.iso

Describe the issue you encountered

During the installation process I chose Spanish language and Spanish latinamercan keyboard. But after the installation, I rebooted and the login screen only has US keyboard (but the keyboard works correctly in spanish latinamerican), and all the system is in English Language.

Steps to reproduce the problem

The previous question describes it. Here is a video of all the process: https://www.youtube.com/watch?v=22tCLeZmers

• 3:30 Language selection
• 4:55 Keyboard selection
• 11:20 Login screen

Include the installation.log:

• Live mode: ~/installation.log
• Installed System: /var/log/installation.log

http://pastebin.com/cNjMrRE7

System setup:
sudo blkid:

/dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="5bab02d6-b4d6-4383-a490-402b338003e1"
/dev/sda2: UUID="f60ecb6d-c33f-3632-93bf-9a42ec9d7703" LABEL="Macintosh HD" TYPE="hfsplus" PARTLABEL="Macintosh HD" PARTUUID="d6b55dfc-ec82-4a97-9b07-9d605bc64f10"
/dev/sda3: UUID="1628e76b-c0d6-462b-af55-ec2914e78294" TYPE="ext4" PARTUUID="b27bb591-bd16-42aa-9623-bc9c9a3c2f73"
/dev/sda4: LABEL="BOOTCAMP" UUID="E32A-1C16" TYPE="vfat" PARTLABEL="BOOTCAMP" PARTUUID="6139fedb-e94e-4ef3-a9a7-139dfeec09d6"
/dev/sdb2: SEC_TYPE="msdos" LABEL="KAOS_EFI" UUID="837E-DA09" TYPE="vfat" PARTUUID="1656e681-02"
/dev/sdb1: UUID="2016-03-11-02-37-37-00" LABEL="KAOS_20160311" TYPE="iso9660" PTUUID="1656e681" PTTYPE="dos" PARTUUID="1656e681-01"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"

sudo fdisk -l:

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3869E466-1D71-40EA-A266-6DEBFAEBF333

Device         Start       End   Sectors   Size Type
/dev/sda1         40    409639    409600   200M EFI System
/dev/sda2     409640 390804063 390394424 186.2G Apple HFS/HFS+
/dev/sda3  390805504 781461503 390656000 186.3G Linux filesystem
/dev/sda4  781461504 976773119 195311616  93.1G Microsoft basic data


Disk /dev/sdb: 7.2 GiB, 7748222976 bytes, 15133248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1656e681

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1  *        0 3608831 3608832  1.7G  0 Empty
/dev/sdb2         220   63707   63488   31M ef EFI (FAT-12/16/32)




Disk /dev/loop0: 10.7 MiB, 11177984 bytes, 21832 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 45 MiB, 47140864 bytes, 92072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.6 GiB, 1729245184 bytes, 3377432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

gdb output:

[live@localhost ~]$ sudo gdb calamares
Password:
GNU gdb (GDB) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from calamares...Reading symbols from /usr/lib/debug//usr/bin/calamares.debug...done.
done.
(gdb) run
Starting program: /usr/bin/calamares
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0x7fffea140700 (LWP 10191)]
01:27:09 [1]: Calamares version: 2.0.90.20160310-git-master-5f86bbc-dirty
Translation: Calamares: Using default locale, system locale one not found: "en_US"
Translation: Qt: Using default locale, system locale one not found: "en_US"
01:27:09 [1]: Default font =====
Pixel size:    -1
Point size:    10
Point sizeF:   10
Font family:   "Noto Sans"
Metric height: 18
01:27:09 [1]: Font height: 18
01:27:09 [1]: Available languages: ("ast", "ca", "cs", "de", "en", "es", "es_AR", "fr", "hr", "hu", "id_ID", "it", "nl_NL", "pl", "pt_BR", "pt_PT", "ru", "sl", "sr_RS", "sv", "tr_TR")
01:27:09 [1]: CalamaresApplication thread: 0x676180
01:27:09 [1]: Using log file: "/root/.cache/Calamares/Calamares/Calamares.log"
01:27:09 [1]: Using Calamares settings file at "/usr/share/calamares/settings.conf"
01:27:09 [1]: Using Calamares branding file at "/usr/share/calamares/branding/kaos_branding/branding.desc"
01:27:09 [1]: Loaded branding component "kaos_branding"
01:27:09 [1]: Proposed window size: 1080 648
01:27:09 [1]: Initial locale  "en_US"
01:27:09 [1]: ViewModule loading self for instance "welcome@welcome"
ViewModule at address 0x7684d0
Calamares::PluginFactory at address WelcomeViewStepFactory(0x744ea0)
ViewStep at address WelcomeViewStep(0x8d5180)
01:27:10 [1]: ViewModule loading self for instance "webview@webview"
ViewModule at address 0x9515f0
Calamares::PluginFactory at address WebViewStepFactory(0x676720)
ViewStep at address WebViewStep(0x961b30)
01:27:10 [1]: ViewModule loading self for instance "license@license"
ViewModule at address 0x9620e0
Calamares::PluginFactory at address LicenseViewStepFactory(0x962b40)
ViewStep at address LicenseViewStep(0x962800)
[New Thread 0x7fffd46e5700 (LWP 10193)]
01:27:10 [1]: ViewModule loading self for instance "locale@locale"
ViewModule at address 0x972830
Calamares::PluginFactory at address LocaleViewStepFactory(0x979660)
ViewStep at address LocaleViewStep(0x97b690)
No layout variant specified on the command line
Trailing -variant option ignored
01:27:10 [1]: xkbmap selection changed to:  "es" - ""
01:27:10 [1]: ViewModule loading self for instance "keyboard@keyboard"
ViewModule at address 0x75ed20
Calamares::PluginFactory at address KeyboardViewStepFactory(0x981160)
ViewStep at address KeyboardViewStep(0xb0ffd0)
01:27:13 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:13 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:13 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:13 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:14 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:14 [1]: LIST OF DETECTED DEVICES:
node    capacity        name    prettyName
01:27:14 [1]: "/dev/sda" 500105249280 "ATA APPLE HDD ST500L" "ATA APPLE HDD ST500L – 465.76 GiB (/dev/sda)"
01:27:14 [1]: "/dev/sdb" 7748213760 "TDK LoR TF10" "TDK LoR TF10 – 7.22 GiB (/dev/sdb)"
01:27:20 [1]: "Osprober lines, clean:\n"
01:27:20 [1]: Found EFI system partition at "/dev/sda1"
01:27:20 [1]: ViewModule loading self for instance "partition@partition"
ViewModule at address 0x2d40170
Calamares::PluginFactory at address PartitionViewStepFactory(0x2d6b030)
ViewStep at address PartitionViewStep(0x961a10)
01:27:20 [1]: ViewModule loading self for instance "users@users"
ViewModule at address 0x2dc95d0
Calamares::PluginFactory at address UsersViewStepFactory(0x2dcab60)
ViewStep at address UsersViewStep(0x2dc9b60)
01:27:20 [1]: ViewModule loading self for instance "summary@summary"
ViewModule at address 0x97a230
Calamares::PluginFactory at address SummaryViewStepFactory(0x2df13b0)
ViewStep at address SummaryViewStep(0x2df1800)
01:27:20 [1]: Module "partition@partition" already loaded.
[New Thread 0x7fffd2ab9700 (LWP 10896)]
01:27:20 [1]: QML import paths: ("/usr/share/calamares/qml", "/usr/bin", "/usr/lib/qt5/qml")
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: Module "locale@locale" already loaded.
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: Module "keyboard@keyboard" already loaded.
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: Module "users@users" already loaded.
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: LAST VS IS EVS!
01:27:20 [1]: ViewModule loading self for instance "finished@finished"
ViewModule at address 0x2e95d50
Calamares::PluginFactory at address FinishedViewStepFactory(0x2e95a10)
ViewStep at address FinishedViewStep(0x2e89820)
01:27:20 [1]: Need at least storage bytes: 7516192768
01:27:20 [1]: Need at least ram bytes: 1073741824
01:27:20 [1]: A battery exists, checking for mains power.
01:27:20 [1]: enoughStorage, enoughRam, hasPower, hasInternet, isRoot:  true true true true true
01:27:20 [1]: Updating partitioning state widgets.
01:27:20 [0]: QCoreApplication::postEvent: Unexpected null receiver
01:27:21 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:21 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:21 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:21 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:27:22 [1]: Required  storage B: 10200547328 "(9GB)"
01:27:22 [1]: Available storage B: 187740160 "(0GB)"
01:27:22 [1]: Required  storage B: 10200547328 "(9GB)"
01:27:22 [1]: Available storage B: 196679585792 "(183GB)"
01:27:22 [1]: Partition "/dev/sda3" authorized for resize + autopartition install.
01:27:22 [1]: Updating partitioning preview widgets.
01:27:22 [0]: QCoreApplication::postEvent: Unexpected null receiver
01:27:25 [1]: Selected locale "es_ES"
[New Thread 0x7fffcad7a700 (LWP 10937)]
[New Thread 0x7fffca579700 (LWP 10938)]
[New Thread 0x7fffc9d78700 (LWP 10939)]
[New Thread 0x7fffc9577700 (LWP 10940)]
[New Thread 0x7fffc8d76700 (LWP 10941)]
[New Thread 0x7fff83ffd700 (LWP 10942)]
01:27:40 [1]: Updating partitioning preview widgets.
01:27:40 [0]: QCoreApplication::postEvent: Unexpected null receiver
[Thread 0x7fffd46e5700 (LWP 10193) exited]
01:27:41 [1]: Choice applied:  4
01:27:56 [1]: Found EFI system partition at "/dev/sda1"
01:28:10 [1]: Found EFI system partition at "/dev/sda1"
01:28:32 [0]: QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
01:28:33 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:28:33 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:28:33 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:28:34 [0]: QFileInfo::absolutePath: Constructed with empty filename
01:28:34 [1]: PartitionCodeModule has been asked for jobs. About to return: "Limpiar todos los montajes temporales.\nLimpiar montajes para las operaciones de particionado en /dev/sda\nRedimensionar partición /dev/sda1.\nFormatear partición /dev/sda3 (sistema de archivos: ext4, tamaño: 190750 MB) en ATA APPLE HDD ST500L.\nEstablecer la información de la partición"
01:28:34 [0]: QString::arg: Argument missing: "Redimensionar la partición <strong>/dev/sda1</strong> de <strong>2MB</strong> a <strong>199MB</strong>." , 199
01:28:34 [0]: QString::arg: Argument missing: "Redimensionar la partición <strong>/dev/sda1</strong> de <strong>2MB</strong> a <strong>199MB</strong>." , 199
01:28:34 [1]: Gathering UUIDs for partitions that exist now.
01:28:34 [1]: QHash(("/dev/sdb2", "837E-DA09")("/dev/sda2", "f60ecb6d-c33f-3632-93bf-9a42ec9d7703")("/dev/sda3", "a0bd83b0-9c69-436f-86fc-547ef6800c4e")("", "")("/dev/sda1", "67E3-17ED")("/dev/sda4", "E32A-1C16"))
01:28:34 [1]: Writing to GlobalStorage["partitions"]
01:28:34 [1]: "/dev/sda1" mtpoint: "/boot" fs: "fat32" "67E3-17ED"
01:28:34 [1]: "/dev/sda2" mtpoint: "" fs: "hfsplus" "f60ecb6d-c33f-3632-93bf-9a42ec9d7703"
01:28:34 [1]: "/dev/sda3" mtpoint: "/" fs: "ext4" "a0bd83b0-9c69-436f-86fc-547ef6800c4e"
01:28:34 [1]: "/dev/sda4" mtpoint: "" fs: "fat32" "E32A-1C16"
01:28:34 [1]: "/dev/sdb2" mtpoint: "" fs: "fat16" "837E-DA09"
01:28:34 [1]: "" mtpoint: "" fs: "unknown" ""
01:28:34 [1]: Gathering UUIDs for partitions that exist now.
01:28:34 [1]: QHash(("/dev/sdb2", "837E-DA09")("/dev/sda2", "f60ecb6d-c33f-3632-93bf-9a42ec9d7703")("/dev/sda3", "a0bd83b0-9c69-436f-86fc-547ef6800c4e")("", "")("/dev/sda1", "67E3-17ED")("/dev/sda4", "E32A-1C16"))
01:28:34 [1]: Writing to GlobalStorage["partitions"]
01:28:34 [1]: "/dev/sda1" mtpoint: "/boot" fs: "fat32" "67E3-17ED"
01:28:34 [1]: "/dev/sda2" mtpoint: "" fs: "hfsplus" "f60ecb6d-c33f-3632-93bf-9a42ec9d7703"
01:28:34 [1]: "/dev/sda3" mtpoint: "/" fs: "ext4" "a0bd83b0-9c69-436f-86fc-547ef6800c4e"
01:28:34 [1]: "/dev/sda4" mtpoint: "" fs: "fat32" "E32A-1C16"
01:28:34 [1]: "/dev/sdb2" mtpoint: "" fs: "fat16" "837E-DA09"
01:28:34 [1]: "" mtpoint: "" fs: "unknown" ""
01:28:45 [1]: loading ok  
01:28:45 [1]: PartitionCodeModule has been asked for jobs. About to return: "Limpiar todos los montajes temporales.\nLimpiar montajes para las operaciones de particionado en /dev/sda\nRedimensionar partición /dev/sda1.\nFormatear partición /dev/sda3 (sistema de archivos: ext4, tamaño: 190750 MB) en ATA APPLE HDD ST500L.\nEstablecer la información de la partición"
[New Thread 0x7fffd46e5700 (LWP 11025)]
01:28:45 [0]: Starting job "Limpiar todos los montajes temporales."
01:28:45 [1]: Opened mtab. Lines:
01:28:45 [1]: "union / aufs rw,relatime,si=9c65707728849c8f 0 0"
01:28:45 [1]: "/dev/sdb1 /bootmnt iso9660 ro,relatime 0 0"
01:28:45 [1]: "dev /dev devtmpfs rw,nosuid,relatime,size=1969576k,nr_inodes=492394,mode=755 0 0"
01:28:45 [1]: "tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0"
01:28:45 [1]: "devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0"
01:28:45 [1]: "hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0"
01:28:45 [1]: "mqueue /dev/mqueue mqueue rw,relatime 0 0"
01:28:45 [1]: "proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0"
01:28:45 [1]: "systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0"
01:28:45 [1]: "sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0"
01:28:45 [1]: "securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0"
01:28:45 [1]: "tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0"
01:28:45 [1]: "cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0"
01:28:45 [1]: "pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0"
01:28:45 [1]: "efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0"
01:28:45 [1]: "debugfs /sys/kernel/debug debugfs rw,relatime 0 0"
01:28:45 [1]: "configfs /sys/kernel/config configfs rw,relatime 0 0"
01:28:45 [1]: "run /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0"
01:28:45 [1]: "tmpfs /tmp tmpfs rw,nosuid,nodev,relatime 0 0"
01:28:45 [1]: "tmpfs /tmp tmpfs rw,nosuid,nodev,relatime 0 0"
01:28:45 [1]: "union /var/tmp aufs rw,relatime,si=9c65707728849c8f 0 0"
01:28:45 [1]: "tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=395552k,mode=700,uid=1000,gid=100 0 0"
01:28:45 [1]: "fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0"
01:28:45 [1]: ClearTempMountsJob finished. Here's what was done:
 ""
01:28:45 [0]: Starting job "Limpiar montajes para las operaciones de particionado en /dev/sda"
01:28:46 [1]: ClearMountsJob finished. Here's what was done:
 ""
01:28:46 [0]: Starting job "Redimensionar partición /dev/sda1."
01:28:46 [0]: "- Verificando el sistema de ficheros de la partición /dev/sda1."
[Thread 0x7fffd46e5700 (LWP 11025) exited]
01:28:46 [0]: Installation failed:
01:28:46 [0]: - message: "La verificación del sistema de ficheros de la partición /dev/sda1 ha fallado."
01:28:46 [0]: - details: "==========================================================================================\nCommand: fsck.msdos -a -w -v /dev/sda1\n==========================================================================================\nfsck.fat 3.0.28 (2015-05-16)\n\n"
01:28:53 [0]: Calamares will now quit.
[Thread 0x7fffca579700 (LWP 10938) exited]
01:28:53 [0]: QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
01:28:53 [0]: QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
[Thread 0x7fffea140700 (LWP 10191) exited]
[Thread 0x7fff83ffd700 (LWP 10942) exited]
[Thread 0x7fffc8d76700 (LWP 10941) exited]
[Thread 0x7fffc9577700 (LWP 10940) exited]
[Thread 0x7fffc9d78700 (LWP 10939) exited]
[Thread 0x7fffcad7a700 (LWP 10937) exited]
[Thread 0x7fffd2ab9700 (LWP 10896) exited]
[Inferior 1 (process 10187) exited normally]
(gdb) thread apply all bt

Submission type

• Bug report
• Feature Request

KaOS ISO date you are having issues with or have a request for

KaOS 2017.04 (both variants, the normal one and the wayland

How did you create the Live Media?

dd under Linux onto an USB stick

Did you check the md5sum of the downloaded ISO?

no.

Describe the issue you encountered

calamares crashed on two machines with two different ISO origins. Started from welcome and standalone. Pre- and post-updates on the live-system.

Steps to reproduce the problem

dd an ISO on an USB-stick, just boot, start install. Crash.

Include the installation.log:

See Bug Report 7a95b45f-72dd-c510-4f03806c-57a25a90
there must be an other Bug Report created on the other machine.

• Live mode: ~/installation.log

13:33:43 [1]: Calamares version: 3.1.0.20170409-git-master-e44b7e3
13:33:43 [1]: Default font =====
Pixel size: -1
Point size: 10
Point sizeF: 10
Font family: "Noto Sans"
Metric height: 18
13:33:43 [1]: Font height: 18
13:33:43 [1]: Available languages: ("ast", "ca", "cs", "de", "en", "es", "es_AR", "fr", "hr", "hu", "id_ID", "it", "nl_NL", "pl", "pt_BR", "pt_PT", "ro_RO", "ru", "sl", "sr_RS", "sv", "tr_TR")
m_crashReporterWChar: /usr/bin/../libexec/calamares_crash_reporter13:33:43 [1]: CalamaresApplication thread: 0xdebad0
13:33:43 [1]: Using log file: "/root/.cache/Calamares/Calamares/Calamares.log"
13:33:43 [1]: Using Calamares settings file at "/usr/share/calamares/settings.conf"
13:33:43 [0]: ASSERT: "config.IsMap()" in file /buildsys/apps/calamares/src/calamares/src/libcalamaresui/Settings.cpp, line 61
13:33:44 [1]: Arguments list: "/usr/bin/../libexec/calamares_crash_reporter, /tmp/7a95b45f-72dd-c510-4f03806c-57a25a90.dmp, 4818, 6, Calamares, /usr/bin/calamares, 3.1.0.20170409-git-master-e44b7e3, 4818"

• Installed System: /var/log/installation.log
  I can't install.

CPU of the first machine is an AMD E350
CPU of the second machine is an Intel Pentium J3710

First run to KaOS installation.

PC configs
$lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation C220 Series Chipset Family H81 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode](rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)

Chosen options :

• Installing via select a partition
• Manual Partitioning with ext4 type

Installer failed with the following screen.

Hello!
I am satisfy KaOS Linux on my Dell Optiplex 760 and Dell Latitude D630 (first desktop second laptop both Intel Core 2 Duo).
But I bought new laptop called Hyperbook. You can see (and buy) it on this page:
https://tinyurl.com/towknj3
This is screenshot from UEFI Bios with info about its main components:

Yesterday I struggle few hours to force KaOS installer to work. Without success.
It boot to main menu and failed load linux kernel - it only shows:
sha256 verified
No mater how I tune kernel command line - nothing helps (I disable other drivers, enable logs, force to use xwindow, type: random.trust_cpu=1 - in many combinations). I also dissable and enable secure boot. Suprisingly when I disable secure boot and clear all its data (in UEFI menu) I note that KaOS installer add sha256 key with all zeros to Administer Secure Boot -> DBX Option
So I try Kubuntu 19.10 - and it install without any problems!
Today I decide to report my problems with KaOS installer (because I am highly motivated user - I appreciate your effort and I am donor to KaOS budget). So I write KaOS installer image to my USB stick and try to boot. Surprisingly it started! But after this I was unable to connect to WiFi - no networks found. But I try once more start KaOS installer but this time without other video drivers than Intel and with proprietary drivers. This time I see my networks but they were greyed out and this was hardly even to highlight (after move mouse over network) to see "Connect" button. This look like this:

I not try installation with out network - this is probably use less and I don't suppose to solve this problems after installation.
Please let me know how to install KaOS with network. I want use it an I will pay for it as long as I can afford.

Submission type

• [ x] Bug report
• Feature Request

Info regarding which version of Calamares is used, which Distribution

… 3.2.1 KaOS

Provide information on how the disks are set up, in detail, with full logs of commands issued

… I choose "delete partition" (see installation.log)

Describe the issue you encountered

…
installation.log

Is your feature request related to a problem? Please describe.
Bootldr module have a for loop to find a boot partition.
This loop suppose that the partition number is a single digit.

Describe the solution you'd like
I'd like it to support multiple digits numbers, like /dev/sda143.

Describe alternatives you've considered
I once edited main.py to have:

        for partition in partitions:
            if partition["mountPoint"] == "/boot":
                libcalamares.utils.debug(partition["device"])
                boot_device = partition["device"]
                boot_p = ''.join([s for s in boot_device if s.isdigit()])
                device = ''.join([s for s in boot_device if not s.isdigit()])

where the last two lines are my proposed change...
it could be problematic with a device like /dev/hd2p3 where it would give boot_p of 23, and device /dev/hdp... but I don't really know such device names in use.

Additional context
I have just cloned this repository, and will try to get a pull request (which I am not used to do).