Introduction

Fedora Linux 44 has arrived, bringing exciting updates to the Atomic Desktop variants—Silverblue, Kinoite, Sway Atomic, Budgie Atomic, and COSMIC Atomic. This guide walks you through the upgrade process, highlighting key changes you need to handle before and after updating. By following these steps, you'll ensure a smooth transition without losing data or breaking your workflow. Let's dive in.

What You Need

• An existing Fedora Atomic Desktop (version 43 or earlier) installed
• Stable internet connection for downloading updates
• Administrative privileges (sudo) on your system
• Backup of important data, especially if using Plasma Vaults with legacy backends
• Access to a terminal (or use GNOME Console/KDE Konsole)

Step-by-Step Upgrade Guide

Step 1: Check for FUSE 2 Dependencies

Fedora 44 removes FUSE version 2 libraries. This can affect AppImages and KDE Plasma Vaults using old backends. First, identify if you rely on these.

Check AppImages

Run the following command on each AppImage file to see its runtime version:

readelf -a /path/to/appimage | grep -i fuse

If it references libfuse2, it's using an old runtime. Make a list of such AppImages.

Check Plasma Vaults

Open System Settings > Vaults. If you see vaults using EncFS or CryFS, note their names and ensure you have the encryption password handy.

Step 2: Migrate Plasma Vaults Before Upgrade

KDE recommends switching to the gocryptfs backend. Follow these steps before upgrading:

1. Create a new vault using gocryptfs: Open Vaults settings, click Add New Vault, choose gocryptfs.
2. Mount both the old and new vaults.
3. Copy all data from the old mount point to the new one.
4. Unmount and remove the old vault.

If you've already upgraded and lost access, see Step 6 below.

Step 3: Upgrade System to Fedora 44

The standard upgrade path for Atomic Desktops is via rpm-ostree. In a terminal:

1. sudo rpm-ostree upgrade
2. When prompted, reboot into the new deployment: sudo systemctl reboot
3. At the boot menu, select the entry labeled Fedora 44 (if not default).

After booting, verify version: rpm-ostree status.

Step 4: Handle Broken AppImages

If some AppImages stopped working after upgrade, try these alternatives in order:

• Check for a Flatpak version of the app from Flathub. Install it: flatpak install flathub app.id
• Update the AppImage itself. Download the latest release from upstream; newer versions often use a compatible FUSE3 runtime.
• Report the issue to the AppImage author. Mention that Fedora 44 no longer ships FUSE2, and ask them to repackage with an updated runtime.

If you absolutely need the old AppImage and can't find alternatives, you can layer FUSE2 manually (see Tips below).

Step 5: Adopt New Documentation & Issue Tracker

Fedora Atomic Desktops now have unified documentation hosted on the new Fedora forge. Visit the official docs for guides on Silverblue, Kinoite, and other variants. To report issues affecting all variants, use the cross-variants tracker on the new forge. For desktop-specific issues, refer to each SIG's tracker linked from the README.

If You Need Translation Help

The previous translations were not migrated. If you speak a language other than English, consider helping translate the new docs. Most content is copy/paste from the old version—contact the Atomic Desktops SIG to get started.

Step 6: Recover EncFS/CryFS Vaults If Already Upgraded

If you upgraded without migrating your EncFS or CryFS vault, they are now inaccessible. To recover your data:

1. Layer the required package: sudo rpm-ostree install cryfs (or fuse-encfs for EncFS).
2. Mount the vault manually or via System Settings (the layer should restore the backend).
3. Follow Step 2 above to migrate the data to a gocryptfs vault.
4. Once migrated, remove the layered package: sudo rpm-ostree reset (this resets all overlays; ensure you have no other layered packages you need).

Tips and Final Considerations

• Always back up important data before any major upgrade.
• If you use AppImages frequently, consider encouraging upstream developers to adopt FUSE3 runtimes.
• The legacy pkla Polkit rules format is no longer supported. Custom rules must use the .rules format. If you had custom .pkla files, they will be ignored after upgrade. Convert them to JavaScript rules using polkit.
• After upgrade, check journalctl -p 3 -b for any messages about missing FUSE2 or broken rules.
• If you need to temporarily restore FUSE2 for a critical AppImage, you can layer fuse2-libs from RPM Fusion, but this is not recommended long-term.
• Explore the new unified docs—they cover all Atomic Desktops in one place, making it easier to find answers.

By following these steps, you'll be well-equipped to enjoy Fedora 44 Atomic Desktops with minimal disruption. Happy upgrading!