News report

Fedora 45 Beta Enforces RPM Signatures and Switches to kmscon

Fedora Linux 45 Beta is available with stricter RPM signature verification, kmscon replacing the legacy kernel console, and major developer-stack updates.

On this page
  1. Fedora 45 Beta is available for testing
  2. RPM itself now rejects unsigned packages by default
  3. kmscon replaces the old framebuffer console
  4. Developer environments get several compatibility-sensitive updates
  5. Fedora 45 is more than the GNOME 51 update

Fedora 45 Beta is available for testing

Fedora Linux 45 Beta is now available across Workstation, KDE Plasma Desktop, Server, Cloud and IoT editions, with beta content also provided for Fedora Atomic Desktops, Spins and Labs subject to several image exceptions. Fedora published the beta on September 15 as the public test milestone ahead of the final Fedora 45 release.

GNOME 51 and other visible desktop updates are part of the release, but two lower-level changes are especially relevant to PC users and developers: RPM now requires valid package signatures by default, and Fedora replaces the legacy in-kernel fbcon console with the userspace kmscon terminal.

RPM itself now rejects unsigned packages by default

Fedora has long verified repository packages through higher-level tools such as DNF. Fedora 45 tightens the lower layer as well: RPM changes its default package-verification mode from digest checking to full signature-and-digest verification. An unsigned package, or one whose signature cannot be verified with an imported key, is therefore rejected by RPM unless the user explicitly overrides signature checking.

This is more consequential for local package-building and manual RPM workflows than for ordinary Fedora repository updates. Fedora documents an explicit --nosignature override, while RPM 6.0 can automatically sign locally built packages after a one-time setup. Mock and COPR also have signing paths intended to keep development and build workflows functional under the stricter default.

kmscon replaces the old framebuffer console

Fedora 45 also moves its virtual-terminal console away from fbcon, the terminal emulator that runs inside the Linux kernel, to kmscon in userspace. kmscon uses Linux Kernel Mode Setting and DRM graphics infrastructure rather than depending on the older framebuffer-emulation path used by fbcon.

Fedora says the change provides smoother rendering, improved Unicode and font handling, and better system stability. The project proposal also describes security and maintenance benefits: fbcon is not well maintained, while modern GPU drivers already use DRM and only retain framebuffer emulation for compatibility with older infrastructure.

Developer environments get several compatibility-sensitive updates

Fedora 45 Beta also carries Podman 6, Pandas 3, Python 3.15, Go 1.27, GCC 16.2 and glibc 2.44 among its updated development stack. Desktop secret management is being standardized around oo7, and Atomic Desktop ISO generation moves to image-builder. These are independent changes rather than one coordinated compatibility break, but together they make the beta useful for testing development machines before Fedora 45 reaches stable release.

That testing distinction matters. This is still a beta, so developers with production workstations should use it to find package, container, driver and local-RPM workflow problems rather than treating the beta label as equivalent to a finished stable upgrade. Fedora maintains a public common-issues path for release-specific problems discovered during testing.

Fedora 45 is more than the GNOME 51 update

Core Tech Tips has separate coverage of GNOME 51 because GNOME is an upstream desktop release used by multiple Linux distributions. Fedora 45 is a broader operating-system change: its package-verification policy, virtual console, development toolchain, installer and image-building changes exist independently of the GNOME desktop.

For a typical Fedora desktop user, the stricter RPM behavior may remain mostly invisible until a manually downloaded or locally built package lacks a verifiable signature. For developers and administrators who work directly with RPMs or low-level consoles, Fedora 45 changes defaults that are worth testing before the stable release arrives.

Go deeper

Related Core Tech Tips coverage

Sources

Primary and technical sources

These sources support the reporting and analysis above. Current stories are updated when later evidence materially changes the facts.

  1. 01 Fedora Magazine

    Announcing Fedora Linux 45 Beta
  2. 02 Fedora Project

    Fedora 45 Change Set
  3. 03 Fedora Project

    Enforcing signature checking by default
  4. 04 Fedora Project

    Use kmscon as default VT console

Related