Upgrading to Fedora 44: A Complete Guide for Atomic Desktop Users

Overview

Fedora Linux 44 introduces significant changes for Atomic Desktop variants—Silverblue, Kinoite, Sway Atomic, Budgie Atomic, and COSMIC Atomic. This guide walks you through every update, from the new issue tracker to the removal of FUSE version 2 libraries. Whether you're a daily driver or a developer, understanding these changes will ensure a smooth upgrade and help you avoid common pitfalls.

By the end of this tutorial, you'll know how to check your AppImages, migrate Plasma Vault backends, and navigate the new documentation. Let's dive in.

Prerequisites

Before you begin, ensure you have:

• A running Fedora Atomic Desktop (any variant) on version 43 or earlier.
• Administrative access (sudo privileges) to update and install packages.
• Backup of important data, especially if you use Plasma Vault with EncFS or CryFS.
• Internet connection for downloading updates.

Optional but recommended: Familiarity with rpm-ostree commands and Flatpak basics.

Step-by-Step Instructions

1. Preparing for the Upgrade

Before upgrading to Fedora 44, it's wise to check your current system for any potential issues. Run the following commands to update your existing packages and confirm your variant:

sudo rpm-ostree update
rpm-ostree status

Take note of any layered packages—you may need to manage them later.

2. Understanding the New Issue Tracker

The cross-variant issue tracker has moved to the new Fedora forge. This is where you should report bugs affecting all Atomic Desktops. For variant-specific issues (e.g., only Silverblue), use the respective SIG trackers listed in the atomic-desktops README.

• Cross-variant issues: file at the new forge under atomic-desktops.
• Variant-specific issues: refer to each SIG's tracker (links in the README).

3. Accessing the Unified Documentation

The unified documentation for all Atomic Desktops is now live on the new forge. Unfortunately, translations were not migrated. If you relied on translated docs, you can help by re‑translating once the setup is ready. The tracking issue is atomic-desktops#10.

To access the documentation, visit the new forge URL (refer to the official Fedora wiki for the exact link).

4. Handling FUSE Version 2 Removal

Fedora 44 removes FUSE 2 libraries from the images. This affects two main areas:

• AppImages using old runtimes.
• Plasma Vault backends depending on FUSE 2 (EncFS and CryFS).

4.1 Checking if Your AppImages Still Work

Some AppImages rely on an older runtime that requires FUSE 2. To check an AppImage’s runtime version, run:

./your-appimage --appimage-extract-and-run 2>&1 | head -1

If you see errors about missing libraries, your AppImage likely uses FUSE 2. Options:

• Look for a Flatpak version of the same application (flatpak search <appname>).
• Report the issue to the upstream developer, asking them to update to a newer AppImage runtime (e.g., AppImageKit ≥ 13).

Temporary workaround: You can layer the fuse2 package (if absolutely necessary) but this is not recommended long‑term.

4.2 Migrating Plasma Vault Backends

KDE no longer supports EncFS and CryFS backends for Plasma Vault. Before updating to Fedora 44, migrate your data:

1. Open Plasma Vault and unlock your existing vault.
2. Copy the contents to a temporary location (e.g., /tmp/vaultbackup).
3. Remove the old vault.
4. Create a new vault using the gocryptfs backend.
5. Restore your data from the backup.

If you already updated and need access, layer the required packages temporarily:

sudo rpm-ostree install cryfs fuse-encfs

Then migrate your data, and finally remove the layered packages:

sudo rpm-ostree reset

5. Removing pkla Polkit Rules Support

Fedora 44 drops compatibility for the legacy pkla Polkit rules format. If you have custom pkla files, they will stop working. Convert them to the modern JavaScript (rules) format. Check for pkla files with:

ls /etc/polkit-1/localauthority/

If you find any, refer to the Polkit documentation for conversion steps.

Common Mistakes and How to Avoid Them

• Ignoring the FUSE 2 removal until after upgrade – You might lose access to AppImages or encrypted vaults. Always check before updating.
• Using rpm-ostree install without resetting – Layering packages for temporary fixes (like FUSE 2) should be followed by a reset to avoid bloat.
• Not backing up vault data – If you run the upgrade before migrating, you might temporarily lose access. Use the layered workaround only as a last resort.
• Filing variant-specific issues in the new forge – This clogs the tracker. Always check the README for the correct SIG tracker.
• Assuming AppImages will work with Flatpak runtime – Not all AppImages have Flatpak equivalents; check availability first.

Summary

Upgrading to Fedora 44 on Atomic Desktops requires attention to three main changes: the new issue tracker and documentation location, the removal of FUSE 2 libraries affecting AppImages and Plasma Vault backends, and the end of pkla Polkit support. By following this guide, you can migrate smoothly: check your AppImages, move any EncFS/CryFS vaults to gocryptfs, and convert any pkla rules. Remember to use the correct bug tracker and help with documentation translation if you can. For more details, refer to the official Fedora Change page and the tracking issue.