https://bugs.kde.org/show_bug.cgi?id=480856
Bug ID: 480856 Summary: Fresh Neon install can't boot if encryption is used (20240201-0717 iso) Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: metal...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I'm trying to do a fresh install of KDE Neon, but the current installer appears to be broken. I've been running a previous version of Neon for several years, & its installer works without issue. The previous working ISO was 20220324-0945; the current failing one is 20240201-0717. Rero: 1) Download the ISO, copy to USB & boot live 2) Once booted, connect to wifi & launch the installer 3) On the Partitions step, choose "Manual Partitioning": * Select free space->Create. File System=btrfs, Encrypt=checked, Mount Point=/ * As it's a multi-boot system, I have an existing fat32 efi partition. Select that partition->Edit. Set its mount point to /boot/efi. 4) Proceed with the install 5) Reboot. Result: It prompts for the password, accepts the password, shows the Grub menu, I select Neon, then it fails to boot. The screen shows `cryptsetup: ERROR luks-(uuid): maximum number of tries exceeded`. If I hit a key to show the text, it reveals: ``` /bin/cat: /crypto_keyfile.bin: No such file or directory Nothing to read on input. cryptsetup: ERROR: luks-(uuid): cryptsetup failed, bad password or options? (...repeating over and over until it gives up & drops to shell) ``` * This was the exact install process that worked properly with the previous version of Neon. Just to sanity check my steps, I went back & fully reinstalled the previous 20220324-0945 ISO. It worked without issue. So this definitely seems to be a regression. * I read online that the crrent installer is only broken with encryption & btrfs, so I tried to repeat the process using ext4 rather than btrfs. The same error occurred. * Rather than doing Manual partitioning, I also tried choosing "Replace a partition", and just giving it the partition I intended to use as "/" (aka I didn't explicitly give it /boot/efi). It did not work. Same issue. * I tried doing the same, but *not* selecting encryption (definitely not an option for real-world use, but just out of curiosity). That worked. So it seems to be unable to install with encryption. -- You are receiving this mail because: You are watching all bug changes.