Most Linux distros ship an installer that nobody talks about until it misbehaves. Calamares (the open-source graphical installer framework used by CachyOS, EndeavourOS, KaOS, Fedora Kinoite, and a growing list of others) is exactly that kind of layer. When it works, you barely notice. When it stumbles, you remember. Version 3.4.3 is the kind of release that earns its keep by being mostly invisible, and the three categories of change it ships with are worth understanding before your favorite distro rebuilds against it.
The three changes worth knowing
Disk partitioning got the most attention. The release pulls in the latest KPMcore, the library Calamares uses under the hood for partition manipulation, and adjusts how partition alignment is applied during a guided install. If you have ever installed a Linux box where the boot partition ended up flagged in a way that later confused your bootloader or your initramfs (initial ramdisk, the tiny filesystem your kernel mounts before the real root to bring up storage and services), this is the layer that made those decisions. The 3.4.3 update also closes a specific bug where /boot was being marked as the EFI boot partition. That sounds minor until you remember that systemd’s gpt-auto-generator automatically discovers the EFI system partition by walking the GPT label, and a wrong label means your boot sequence fails in a way that is annoying to recover from.
Locale handling got a quieter fix. The list now spans the Etc/GMT range from -11 all the way through +13, including the artificial zones that do not correspond to any real city or country. The plus-thirteen zone (Etc/GMT+13) only exists because IANA’s tz database (the canonical source of timezone definitions used by every major Unix-like system, maintained by the Internet Assigned Numbers Authority) needs symmetric entries for the Etc/GMT family. Real-world users normally never pick these zones unless they are running a server on edge hardware, a container that has to match a legacy system, or a home lab that needs a deterministic offset for testing. The fix matters for those setups, but is mostly invisible to everyone else.
Wayland keyboard handling was the surprise. Calamares embeds QML (Qt’s QML markup language, used for declarative UI in Qt-based applications like Calamares’ install screens) as part of its installer UI. There was a specific way the embedding interacted with the Wayland session’s input handling that caused keystrokes to drop or repeat during install. The release changes how Calamares hosts its QML views so the glitch stops happening. The fix is plumbing, not features, but plumbing is what makes a tool feel professional instead of fragile.
How to find out which Calamares your distro is shipping
This is the part most coverage skips. Before you evaluate 3.4.3 in your daily distro of choice, you need a way to confirm what version the installer is actually running, because distros rebuild Calamares on their own schedule. Three practical paths:
- During install, the welcome page usually has a small footer or about-link. Open it before you commit to anything; the version string is right there.
- Boot the live ISO and run
calamares --versionin a terminal. Most Calamares-based distros ship the binary on the live image even if it is not in the default path. Ifwhich calamaresreturns nothing, look under/usr/binor/usr/sbin. - After install, the configuration files live under
/etc/calamares. Read thesettings.confnear the top, where the module list and the framework version are listed. Anything in the 3.4.x line means you got the new release; 3.3.x or older means your distro is still catching up. - Grep the install log. Most Calamares-based distros copy a summary into
/var/log/installer/or/var/log/calamares/after the install completes, and the framework version is one of the first lines. That path is the one to check if you came back to the box later and forgot which build you ran.
If your distro is still on a 3.3.x build and you want 3.4.3, the lever is opening a ticket against the maintainer, not trying to install Calamares yourself. The framework is not a package that just sits in your package manager. It is a build target distros integrate into their own installer pipeline, which is why nobody has a one-line upgrade for it.
What changes for users who never read release notes
If you are installing Linux on a real machine today, the practical impact of 3.4.3 sums up as fewer post-install surprises.
- Cleaner partition layouts during guided installs. Specifically, the EFI-versus-/boot mistake that bit some users in earlier builds is now closed in the partition module.
- A complete Etc/GMT zone list. This is invisible unless you are installing in a container or on hardware that needs an artificial zone, but the missing entries were a small papercut for those setups.
- No more dropped or doubled keystrokes on Wayland sessions during install. Anyone who has tried to type a long passphrase into a freshly-installed system will appreciate this one without being told.
None of these are headline features. None of them will show up in marketing copy. The point of 3.4.3 is that the installer feels a little less hand-rolled and a little more like a polished product the next time you fire up a Calamares-based ISO. That is the right kind of release to ship six months after the last one.
What changes for distro maintainers
If you maintain a Calamares-based distro, 3.4.3 is mostly safe to integrate but worth testing in two specific places before flipping the switch for users. First, run the new build against your existing settings.conf and module list. The configuration format is stable, but module interfaces have been polished; any custom module you wrote against an older API should be re-validated. Second, exercise the partitioning module against the UEFI (Unified Extensible Firmware Interface, the modern replacement for BIOS that handles boot-time hardware initialization) and legacy-BIOS paths you intend to support. The KPMcore bump includes partition alignment tweaks that should be invisible, but the EFI-label fix is exactly the kind of change that surfaces in regression tests rather than in casual use.
For CI/CD-minded distros, the Calamares project ships test modules that can be run headlessly. If your distro has any kind of automated installer build, that is the path to catching a regression before your users do. If you do not have that set up yet, a single round of guided-install tests on UEFI hardware and another on legacy BIOS hardware catches most issues. The 3.4.3 changes are small and surgical, so a careful test pass of an hour or two should be enough.
Trade-offs
The release is solid, but it is not free. Updating Calamares in your distro always touches the partition module, which is the layer your installer users trust the most. The 3.4.3 fixes are improvements rather than new features, which means the right time to pick them up is when your next planned installer refresh lands, not on an emergency schedule. Distros that maintain long-lived installers do not need to rush this; distros shipping a fresh build every quarter can absorb it in their normal cadence.
For everyone else, the takeaway is the inverse: do not chase this release. Pick up whatever version your distro gives you, and trust that 3.4.3 is in the queue. The improvements are the kind that compound quietly over years, not the kind you should be checking for by hand.