14 DAY TRIAL // The Calamares team is proud to announce the availability of the sixth maintenance update to the 2.4 stable series of the open-source, distribution-independent system installer Calamares for Linux-based operating systems.
Calamares 2.4.6 comes approximately two months after the release of the previous version, namely Calamares 2.4.5, and as expected, it's a bugfix release that only delivers various improvements and bug fixes for some of the issues reported by users during all this time.
Highlights include support for building Calamares' partition module with either KPMcore 2.2 or KPMcore 3.0, and packagers/system integrators need to know that Calamares 2.4.6 requires KPMcore 2.2, 2.2.1 or 3.0.2. Please keep in mind not to use the KPMcore 3.0 and 3.0.1 releases because they include some critical bugs.
Furthermore, Calamares 2.4.6 improved the build system files to allow the module linkage to default to private, repairs the automatic login handling for the SDDM login manager in the displaymanager module, and addresses an issue in the partition module to allow for setting of the correct flags to a UEFI system partition.
Calamares 2.4.6 is coming soon to a distro near you
Among other noteworthy changes implemented in Calamares 2.4.6, we can mention a patch for a crash with the webview module that occurred during startup if the installer was built with QtWebEngine, as well as a fix for an issue that would not allow the Internet connection status to be written to the GlobalStorage setting.
Other than that, Calamares 2.4.6 addresses two other small issues related to the partition and users modules, allowing the installation of the legacy bootloader on the right disk drive and the disablement of the root password if the user chooses to do so. Calamares 2.4.6 is coming soon to a distro near you, so update immediately, and the source archive is now available for download.
System integrators who choose to ship their own, modified mount.conf files with Calamares are being informed to update them so that they can bind-mount /run/udev, just like the upstream mount.conf file. GRUB bootloader's os-prober instance won't be able to detect existing operating systems if you fail to do so.