Exploring Fedora Atomic Desktops 44: Key Questions Answered

Fedora Linux 44 brings a host of updates to its Atomic Desktop variants—Silverblue, Kinoite, Sway Atomic, Budgie Atomic, and the new COSMIC Atomic. This release focuses on streamlining development, improving documentation, and phasing out outdated technologies. Whether you're a daily user or a contributor, these changes will affect how you interact with your system. Below, we break down the most important modifications in a Q&A format to help you navigate the transition smoothly.

What is new in Fedora Atomic Desktops in Fedora 44?

Fedora 44 introduces several key updates for all Atomic Desktop variants. The issue tracker has moved to the new Fedora forge, making it easier to report cross-variant bugs. A unified documentation site is now live, though translations need rework due to migration. The most impactful change is the removal of FUSE version 2 libraries, which affects some older AppImages and legacy Plasma Vault backends. Additionally, compatibility with the pkla Polkit rules format has been dropped, though this rarely impacts users. These changes aim to modernize the ecosystem and encourage the use of Flatpaks and newer technologies.

Where is the issue tracker now?

The cross-variant issue tracker has been relocated to the new Fedora forge. This centralized location is the preferred place to file bugs or coordinate work that affects all Atomic Desktop variants. For desktop-specific issues, each Special Interest Group (SIG) maintains its own tracker—these are listed in the README of the atomic-desktops organization on the forge. If you're uncertain where to report, start with the cross-variant tracker. This move consolidates efforts and improves visibility across the community.

What about the documentation?

A unified documentation hub for all Atomic Desktops is now live on the new forge. It replaces the previous fragmented guides and covers installation, troubleshooting, and daily use. However, translations from the old system were not migrated, so the community needs help re-translating content once the translation infrastructure is ready. The good news is that the new docs are centralized—you only need to translate once instead of for each variant. Check the tracking issue atomic-desktops#10 for progress and how to contribute.

Why was FUSE 2 removed and what does it mean?

FUSE version 2 was deprecated and unmaintained for years, so Fedora 44 removed it from atomic images. This is a security and maintenance improvement. In practice, two groups are affected: users of older AppImages that rely on the FUSE 2 runtime, and users of Kinoite with legacy Plasma Vault backends (EncFS or CryFS). If you use AppImages, some may stop working—check the runtime version in the Discussion thread. For Plasma Vault, you should migrate to the gocryptfs backend before updating. After the update, you can temporarily layer the old packages to access data, then reset.

What should I do if my AppImages don't work?

If some AppImages fail after upgrading to Fedora 44, first check if they use the old FUSE 2 runtime. Examples of how to do this are in the Discussion thread. Then try these steps:

• Look for a Flatpak version of the same application—it's more secure and future-proof. Encourage the upstream project to distribute via Flathub.
• Report the issue to the AppImage developer, noting that a newer runtime (based on FUSE 3) is required. You can assist them by pointing to the Fedora change.

Flatpak is the preferred distribution method on Atomic Desktops, and many popular apps already support it.

How to handle Plasma Vault backends after FUSE 2 removal?

KDE no longer recommends EncFS or CryFS backends because they depend on FUSE 2. If you use one of these, migrate your data to a new vault using gocryptfs, the only maintained backend. Do this before updating to Fedora 44 if possible. If you've already updated and need access, you can temporarily layer the old packages: run rpm-ostree install cryfs fuse-encfs, then migrate your vault data, and finally reset with rpm-ostree reset. After migration, remove the layered packages. This ensures your vaults remain secure and functional going forward.

What about pkla Polkit rules?

Fedora 44 drops compatibility for the legacy pkla format for Polkit rules. This change is part of the upstream shift to newer, more secure rule formats. It is highly unlikely that you were relying on pkla rules unless you customized system permissions manually. If you encounter permission issues, check your /etc/polkit-1/rules.d/ directory for any .pkla files and convert them to the JavaScript-based format using documented tools. Most users will not notice this change, as default atomic installations never used pkla rules.