Fedora 44: A KDE-Heavy, DevOps-Tinted First Look

Fedora Linux 44 shipped on April 28, 2026, two weeks behind its original date after a late-cycle batch of blockers. I’ve been running it on my KDE daily-driver for a couple of weeks now. It’s the kind of release that doesn’t scream — no single tentpole feature — but if you spend your day on Linux, the cumulative effect is real. Here’s what stood out to me, with a bias toward what I actually noticed.

The shape of the release

A quick cheat sheet of the headline versions:

Even before you get to features, the toolchain bump alone makes 44 a worthwhile upgrade for anyone compiling things in anger.

The KDE story — and it’s a good one

This is the section I’d skip past in most Fedora reviews. Not this time. Fedora KDE Plasma Desktop 44 leans into a real Plasma 6.6 cycle, and there are several changes that you’ll feel within minutes of logging in.

Spectacle gets OCR

Take a screenshot in Spectacle, and you can now pull text directly out of the image — Tesseract-powered, multi-language, copied to the clipboard with one click. As someone who screenshots terminal output, error messages, and the occasional whiteboard photo on the regular, this is the kind of feature that quietly becomes a daily habit within a week.

Wi-Fi by QR code

If your laptop has a camera, you can now point it at a Wi-Fi QR code — the kind hotels and conferences print on table tents — and connect straight from the Networks widget. No keyboard, no fat-fingering a 24- character password, no asking for the network name twice. This is one of those features that sounds gimmicky until the third time you use it in a week.

Per-app volume from the system tray

Plasma’s audio applet now exposes per-application volume sliders directly from the panel, without diving into kmix or pavucontrol. Tiny change, real ergonomic win — especially on a meetings-heavy day where you want browser audio low and the call client loud.

Custom global themes and accent tinting

You can finally save the current combination of theme, plasma style, window decorations, icon set, and color scheme as a new global theme. This was always doable via a config-file dance; now it’s a button. And the window-frame accent color now has a tint intensity slider, which lets you keep your decorations subtle without turning the accent feature off entirely.

Accessibility moves forward

A few quieter additions worth calling out:

• A new Plasma Keyboard on-screen keyboard.
• A grayscale filter in the Color Blindness Correction settings.
• The Zoom and Magnifier tool gains a centered pointer tracking mode that keeps the cursor anchored in the middle of the magnified region instead of pushing the view around as you move.

Plasma Setup wizard

All Fedora KDE variants now ship Plasma Setup, a post-install wizard that handles account creation and initial configuration separately from the OS installer. The big practical win is consistency: KDE Plasma Desktop, KDE Plasma Mobile, and Kinoite now share the same out-of-box experience instead of each doing their own thing.

SDDM → Plasma Login Manager

This is the change you’ll notice first, and it has the most asterisks. Fedora 44 is the first distribution to ship Plasma Login Manager (PLM) by default, replacing SDDM across all KDE variants. PLM was forked from SDDM and the SDDM Breeze theme, so visually it looks familiar. But there’s a real trade-off:

Heads up: PLM does not support arbitrary QML themes. It’s locked to the Breeze theme.

If you had a customized SDDM greeter — a corporate-branded login, an animated background, anything from the SDDM theme store — that customization does not carry over. For most users this is fine; for fleet operators who’d standardized on a custom greeter, it’s a small migration project.

There were also a few reported post-upgrade login issues in the first week. Most resolved themselves with a fresh ~/.cache clear or by reinstalling plasma-workspace — but if you’re upgrading a critical machine, do it on a day where you have time to triage.

DNF5 is finally everywhere

PackageKit — the abstraction layer that GNOME Software, KDE Discover, and a handful of other tools talk to — now uses the DNF5 backend via libdnf5. DNF5 itself has been the default dnf command since Fedora 41, but PackageKit was the last big holdout. With 44 it finally lines up, and the numbers are concrete:

• Metadata refresh that previously took 20–30 seconds drops to under 5.
• Memory consumption during dependency resolution is roughly 40% lower.
• One dependency resolver across CLI and GUI updates — no more “the terminal says one thing, Discover says another” surprises.

If you script around dnf in your provisioning or have Ansible roles that poke at PackageKit, this is a good moment to re-verify your assumptions. The behavior is largely compatible, but the timing characteristics are different enough to expose any sleep-based synchronization you might have accidentally baked in.

NTSYNC pulled in for gaming

Install Wine, Steam, Lutris, Heroic, or Bottles on a fresh Fedora 44 system, and the ntsync kernel module now comes along automatically as a recommended dependency. NTSYNC handles Windows-style thread synchronization primitives at the kernel level instead of emulating them in userspace through Wine — which is a meaningful performance boost across a wide swath of Windows games and applications.

You don’t have to do anything to opt in. If dnf notices a game launcher landing on your system, the module rides along. If you’re on KDE Plasma, this pairs nicely with Plasma 6.6’s stronger Wayland gaming story — the Games Lab spin even switched from Xfce to KDE Plasma this cycle specifically to take advantage of that.

Toolchain: a big year

The GNU toolchain pulled forward in lockstep: GCC 16.1, binutils 2.46, glibc 2.43, and GDB 16.3. On the LLVM side it’s version 22, and CMake jumps to 4.0 — with Ninja as the default generator out of the box.

That last one is a small quality-of-life win that adds up. If your CI images were carrying around an explicit -G Ninja everywhere, you can probably delete it. If you weren’t, your builds just got faster without you doing anything.

Language ecosystems followed:

• Go 1.26
• Ruby 4.0 (a real major bump from 3.4)
• PHP 8.5
• Haskell GHC 9.10 with Stackage 24
• Ansible 13 (from 11) — worth flagging for anyone running an Ansible control node on Fedora; pin or test your collections before flipping the switch, especially anything that touches community.*.

GNOME 50, briefly

I run KDE day-to-day, but GNOME 50 on my secondary laptop has been solid. The highlights: refined color management, improved remote desktop tooling, a meaningful Parental Controls rework, and the usual round of accessibility upgrades. It’s a polish-and-fill-in release on top of the post-49 dynamic-triple-buffering, HDR, and Wayland-only foundations.

If you’re still on GNOME on X11 somewhere — you’re not, but hypothetically — Fedora 44 is the cycle that’s going to make that hurt.

The DevOps angle: image mode and bootc keep marching

None of this is in the marketing materials, but it’s the plumbing that will determine how Fedora and the broader Red Hat ecosystem deploy five years from now:

• Bootupd (phase 1) lands as a unified mechanism for boot loader updates. Small step, but it’s a prerequisite for image-mode being truly hands-off.
• Packit replaces the current CI for dist-git pull-request testing.
• Konflux becomes the pipeline tool for bootc artifacts, and Fedora CoreOS builds have moved from Jenkins to Konflux.
• The broader bootc / image-mode story continues to mature: same Containerfile, same podman build, same registry push — but the artifact is your operating system. The container is the OS, and the same toolchain a developer uses to ship an application image is what an SRE uses to ship a host image. That’s the promise, and 44 is one more brick in the wall.

If you’ve never touched bootc, this is a reasonable cycle to spin up a VM and try the workflow. It’s not production-ready for most people’s servers yet, but it’s close enough that the mental model is worth having in your head.

Quieter changes that matter

These didn’t make any of the marketing slides, but they’re the ones I’ll remember a year from now:

• Anaconda no longer creates default network profiles automatically. If your kickstarts assumed that behavior, double-check them — silent failures here are exactly the kind of thing that bites a week after rollout.
• cert.pem was dropped from the default trust bundle to improve OpenSSL performance. CA trust still works the way you expect; only the redundant file is gone.
• Python’s mock library usage is being eliminated after six releases of deprecation. If you maintain a Python package in the Fedora repos, this is the cycle to verify your tests run cleanly against unittest.mock.

Should you upgrade?

For KDE workstations: yes, and don’t wait. Plasma 6.6 alone earns the upgrade — Spectacle OCR and per-app volume sliders show up in your muscle memory within a week. Just be aware of the PLM caveat if you’ve customized your greeter, and pick an upgrade day when you have time to triage in the rare event that login breaks.

For GNOME workstations: yes, comfortably. The PackageKit/DNF5 alignment makes Software meaningfully snappier, and the toolchain bumps are a free win.

For servers: it’s Fedora — so the usual “only if you’re already opted into a 13-month support window.” But if you are, 43 → 44 is uneventful in the way you want a Fedora upgrade to be. I ran a dnf system-upgrade on two boxes and a VM with no surprises.

I’ll follow up in a few weeks once I’ve put GCC 16.1, Go 1.26, and Ansible 13 through real work. If you’ve hit anything sharp on 44 — especially around PLM or post-upgrade dnf weirdness — ping me. I’d rather hear about it now than find it myself at 2 a.m.