Calamares version: calamares 3.3.14
Distro: KDE Neon 6.3 x86_64.
Steps to reproduce: I was running the installation process using Calamares. The failure occurred during the opening of the Install system itself. The error message shown was: “Executable: neon PID: 2564 SIGNAL: Segmentation fault (11) Time: 30 Apr 2025 15:52:44 UTC”.
Backtrace: [Please insert the backtrace from the “Developer Information” tab here.]
Hardware:
CPU: AMD Ryzen 5 5600X (12) @ 4.651GHz
GPU: AMD ATI Radeon RX 6650 XT / 6700S / 6800S
Memory: 5806MiB / 15916MiB
Motherboard: MS-7C94 1.0
Additional info:
The installer was running in safe mode, and the reporting assistant was disabled. I was prompted to manually report the bug.
DE: Plasma 6.3.4, WM: kwin, Theme: Breeze-Dark, Icons: breeze-dark, Terminal: konsole.
Uptime during the crash: 20 mins.
Resolution: 1920x1080.
Sorry about your experience, it’s a pity Neon does not keep older install images available.
so there’s no way to install Kde neon?
Did you use some custom settings or it crashes with the default?
I downloaded it from the official website, open the installer and the installation window pops up first for 1-2 seconds and then this error
and yes, I used the default settings.
Same as here.
I see it but only when creating a VM in virt-manager.
I wanted to install kde neon on my ssd, I click on the install service, and this error pops up
I did it, I used the official fedora writer downloader and not rufus.
This has been going on for several builds in a row for about a month.
By the way, the installer starts if you do not load from a USB flash drive, but from a fat32 partition through the Windows recovery menu (f11) - Use the device.
It may be worth suggesting trying different USB creation tools.
I have no issues with installs using the last couple of images, other than in qemu virutal machines, via virt-manager. Calamares crashes when opening there. Using them on my computers, I have had no issues, so far.
I use Ventoy, usually, which boots multiple ISO images directly - no ‘flashing’ involved.
Otherwise, I use dd on the command line. Someone notes that they were successful using Rufus on Windows using ‘dd’ mode. Various flashing tools can do things a bit differently from each other, and historically in my experience trying different ones can be useful when there are problems using in ISO.
Everything has been tried for a long time.
In order to create a flash drive, it is enough to format it in fat32, mount the iso and transfer the contents to the flash drive.
No utilities for creating flash drives in DIFFERENT MODES give any result.
When booting from Ventoy, the message is THAT THE KERNEL MUST BE LOADED FIRST and the download stops.
In KDE, if a USB flash drive is inserted, then when KDE Partition Manager is started, it closes. It looks like we have a GLOBAL problem when working with flash drives. As mentioned above, the bootloader starts if you boot from the fat32 PARTITION (the disk, not the flash drive) on which the iso is unpacked, that is, the installer works from the disk, but does not work from the flash drive, the problem is the assembly with flash drives.
With one caveat -this will not work for those who still use legacy MBR booting.
I have had EFI systems that will not boot using this method, though it does depend on the ISO, it seems.
And I still only see the crash when starting Calamares on KDE neon in a virtual machine. No issues on either my laptop or my PC, no matter how I create the USB stick.
Could an unformatted drive, or one needing checks, be a possible culprit for some?
Segmentation fault normally is due to a pointer going outside the designed memory address, probably some typing mistake is making this bug, source code needs revising.
Image from 05.05.2025 - the problem is fixed, the installer starts in any version of iso creation, even after simple copying to a flash drive with fat32, the problem of working with flash drives in KDE Partition Manager is fixed.
BUT when writing the image of 05.05.2025 via KDE Media Writer, the message is INCORRECT SIGNATURE 05.05.2025.iso.sig !!!
I installed neon-user-20250505-1314.iso using Ventoy and had no issues.