Fedora Linux 44 brings a host of updates to the Atomic Desktop variants—Silverblue, Kinoite, Sway Atomic, Budgie Atomic, and the new COSMIC Atomic. This Q&A covers the most important changes, including a new issue tracker, unified documentation, and the removal of FUSE version 2 libraries. We'll also explain how to handle AppImages that may break and how to migrate Plasma Vaults using legacy backends. Whether you're a daily user or a contributor, these answers will help you navigate the latest release smoothly.
What are the biggest changes for all Atomic Desktops in Fedora 44?
Fedora 44 introduces several cross-variant improvements. Most notably, the issue tracker has migrated to the new Fedora forge, making it easier to file bugs that affect all Atomic variants. Unified documentation is now live on the same forge, although translations still need to be re-done once the new translation setup is ready. The removal of FUSE version 2 libraries is a key technical change—it affects AppImages using an old runtime and Plasma Vaults on Kinoite that rely on EncFS or CryFS backends. Compatibility for legacy pkla Polkit rules has also been dropped, though this is unlikely to impact most users. These changes aim to streamline development and improve security across the board.
Where should I report issues that affect multiple Atomic Desktops?
The cross-variant issue tracker has moved to the new Fedora forge. This is the preferred place for filing bugs or coordinating work that impacts all Atomic variants (e.g., Silverblue, Kinoite, Sway Atomic, etc.). If your issue is specific to one desktop environment, each respective SIG maintains its own tracker—you can find links in the atomic-desktops organization README. Using the correct tracker helps developers triage and resolve problems faster. For instance, a bug affecting only GNOME Shell on Silverblue should go to the Silverblue SIG, not the cross-variant tracker. This keeps the main forge focused on shared infrastructure concerns.
What is the new unified documentation, and how do I access it?
The long-awaited unified documentation for all Atomic Desktops is now live, hosted on the new Fedora forge. Instead of separate docs for each variant (Silverblue, Kinoite, etc.), there's a single guide covering common tasks and workflows. Unfortunately, translations from the previous documentation were not migrated. Once the new forge's translation system is ready, volunteers will need to retranslate the content—but most of the work will be copy‑and‑paste from the old docs. This change simplifies maintenance: we translate once, and all variants benefit. You can find the documentation linked from the atomic-desktops organization page. For further details, see the tracking issue.
Why was FUSE version 2 removed, and how does it affect me?
FUSE version 2 has been deprecated and unmaintained for years, so Fedora 44 removes it from the Atomic Desktop images. This directly impacts two areas: AppImages and Plasma Vault backends on Kinoite. Many older AppImages are built with a runtime that depends on FUSE 2 libraries being present on the host system—without them, those AppImages will fail to run. Similarly, Plasma Vaults using EncFS or CryFS (both FUSE 2‑based) are no longer supported. You can check if an AppImage uses the old runtime by examining its metadata (see the Fedora Discussion thread). If you rely on such AppImages, consider switching to Flatpaks or asking upstream to update.
What should I do if an AppImage stops working after upgrading to Fedora 44?
First, verify whether the AppImage uses an old runtime that requires FUSE 2. You can do this by running strings <AppImage> | grep -i fuse (example in the Discussion thread). If it does, here are your options:
- Look for a Flatpak version of the application. Flatpaks are the recommended way to run desktop apps on Atomic Desktops and are fully supported.
- Report the issue upstream and encourage the developers to use a newer AppImage runtime (v2 or later) that doesn't depend on host FUSE 2 libraries.
- Consider helping upstream package as a Flatpak—this benefits the entire community.
As a temporary workaround, you can layer the necessary FUSE 2 libraries via rpm-ostree install fuse2-libs, but this is not recommended long‑term because it breaks the atomic update model.
How do I migrate my Plasma Vault if I used EncFS or CryFS?
KDE upstream no longer recommends EncFS or CryFS backends for Plasma Vaults, primarily because they depend on the now‑removed FUSE 2 libraries. If you have an existing vault using one of these backends, you need to migrate your data to a new vault using the only maintained backend: gocryptfs. Ideally, perform the migration before upgrading to Fedora 44. If you've already upgraded and can't access your data, temporarily layer the required packages by running rpm-ostree install fuse-encfs or cryfs, then migrate your data. After migration, remove the layered packages with rpm-ostree reset to restore a clean image. Detailed steps are available in the tracking issue.
What about the removal of pkla Polkit rules? Should I be concerned?
Fedora 44 drops compatibility for the legacy pkla (PolicyKit Local Authority) format for Polkit rules. This change is part of the broader FUSE 2 cleanup, but its impact is minimal for most users. The pkla format was deprecated long ago in favor of JavaScript‑based rules (.rules files). Unless you or your organization created custom pkla rules—extremely rare on Atomic Desktops—you won't notice any difference. If you do have such custom rules, they will no longer be read. You should convert them to the modern .rules format. For the vast majority of Atomic Desktop users, this removal is transparent and improves system security by removing outdated code.