Fedora Linux 44: 6 Key Updates for Atomic Desktop Users

Fedora Linux 44 has arrived, bringing a host of enhancements specifically tailored for the Atomic Desktop family—Silverblue, Kinoite, Sway Atomic, Budgie Atomic, and COSMIC Atomic. These immutable, container‑friendly spins have become favorites among developers and power users who value stability and atomic updates. This release refines the development workflow, simplifies documentation, and removes legacy components to keep the platform lean. Here are the six most important changes you need to know, each explained with practical implications for your daily workflow.

1. Issue Tracker Moved to the New Fedora Forge

The cross‑variants issue tracker has migrated to the new Fedora Forge—a unified Git infrastructure that modernizes how we report and track bugs. If you encounter a problem that affects all Atomic Desktops (or need to coordinate work across them), this is now the canonical place to file it. For desktop‑specific issues (e.g., only Kinoite or Sway Atomic), the respective Special Interest Group (SIG) trackers still apply. The atomic‑desktops organization’s README includes links to all SIG trackers. This move streamlines collaboration and ensures that cross‑cutting concerns get the visibility they deserve. Existing issues have been migrated automatically, so you can continue where you left off.

2. Unified Documentation Goes Live on the New Forge

After months of effort, the unified documentation for all Atomic Desktop variants is finally available on the new Fedora Forge. Previously, each variant had its own separate docs, leading to duplication and confusion. Now you’ll find a single, coherent guide covering everything from getting started to advanced customization. The translation system hasn’t been migrated yet, so if you contributed translations before, you’ll need to re‑submit them once the setup is ready. Fortunately, the content is mostly copy‑paste from the old docs, so the process should be quick. This centralized approach means that improvements benefit every variant equally, and new additions (like COSMIC Atomic) are automatically included.

3. FUSE Version 2 Libraries Removed

FUSE (Filesystem in Userspace) version 2 has been deprecated upstream for years and is now removed from all Atomic Desktop images. This change has two main consequences. First, some older AppImages that rely on the classic AppImage runtime may stop working. Second, users of Plasma Vault on Kinoite who use the legacy EncFS or CryFS backends need to migrate their data to the supported gocryptfs backend. The Fedora Change and the tracking issue atomic‑desktops#50 provide full details. While this removal may cause temporary inconvenience, it aligns Fedora with modern, maintained libraries and reduces the attack surface of the system.

4. AppImage Compatibility: Check Your Runtime

If you rely on AppImages, some may fail after the update because they use an old runtime that depends on FUSE 2 libraries. To check, run strings <your-appimage> | grep -i fuse; if you see references to libfuse.so.2, the AppImage needs an update. The recommended course of action is to look for a Flatpak version of the same application—Flatpak is the preferred distribution mechanism for immutable Fedora spins. If no Flatpak exists, report the issue to the upstream project and encourage them to update their runtime. You can also consider layering the fuse3 package via rpm-ostree install fuse3 as a temporary workaround, but note that this will persist across updates unless you reset layers. Ultimately, migrating to Flatpak or newer AppImage runtimes is the best long‑term solution.

5. Plasma Vault: Migrate from EncFS/CryFS to gocryptfs

KDE Plasma Vault users on Kinoite must act before updating if they use the EncFS or CryFS backends. These backends rely on the deprecated FUSE 2 libraries and are no longer recommended by upstream. To migrate, first unlock your existing vault, copy the contents to a temporary location, then create a new vault using the gocryptfs backend (the only maintained option). Move your files into the new vault and delete the old one. If you’ve already updated to Fedora 44 and need to access your old data, you can temporarily layer the required package (cryfs or fuse-encfs) with rpm-ostree install, perform the migration, and then reset the layered packages with rpm-ostree reset. Delaying this could leave you locked out of your encrypted folders.

6. Legacy pkla Polkit Rules Dropped

The old pkla format for Polkit authorization rules (used in /etc/polkit-1/rules.d/ with .pkla extensions) has been removed. This format was a remnant from older systems and is now fully replaced by the modern JavaScript‑based rules. In practice, very few users will notice—unless you manually created custom pkla files for privilege escalation, they won’t work after upgrading. Any administrator‑defined rules should be converted to the new syntax. Systems that used the default policies (the vast majority) will see no change. This cleanup reduces maintenance burden and aligns with upstream Polkit’s direction.

Fedora Linux 44 solidifies the Atomic Desktop family as a forward‑looking platform. By moving to the new forge, centralizing documentation, and shedding legacy dependencies, the release improves collaboration, usability, and security. Whether you run Silverblue for development, Kinoite for daily driving, or one of the newer spins like Sway or COSMIC, these updates ensure a smoother, more modern experience. Review the linked issues and plan any necessary migrations—then enjoy the latest Fedora has to offer!