Fedora Miracle, one of the new approved flavors that will arrive in Fedora 41

Fedora

The Fedora 40 edition It is still recent and has not been released long, in this version it isand implemented a large number of changes important and among them, one of those that stood out was the official introduction of the “Atomic Desktops” family, with new desktop environments for the distribution.

And it seems that The trend could continue, since now the FESCo (Fedora Engineering Steering Committee), in charge of the technical part of the development of Fedora Linux, approved the creation of official ISO images which will present a graphical environment based on the composite manager Miracle, which we have already talked about here on the blog.

Miracle-wm stands out for offering support for window mosaics, similar to the i3 window manager, the Hyprland composite manager and the Sway user environment and it is mentioned that the intention is to create a composer that is flashier and more feature-rich than any of those composers, such as swayfx.

It is mentioned that Fedora Miracle Spin will use the Wayland protocol and specific components for building composite managers based on Mir. Fedora Spin Edition with Miracle It will be available starting with the release of Fedora 41.

miracle-wm

miracle-wm capture

The main purpose of this new version is to offer a functional and aesthetic user environment, inspired by the mosaic window design from the i3 window manager and with a focus on vibrant visual effects. This update is primarily aimed at introducing a high-quality Wayland-based environment, compatible with a wide range of devices, including those with low-power ARM and x86 processors.

Another change which was also made in Fedora 41 and which we also already mentioned, is package removal gnome-session-xsession, which is responsible for launching a GNOME session based on the X server. And starting with Fedora 41, the only sessions supported by default in Fedora Workstation will be those based on Wayland, although the X11 session packages will continue to be available in the repositories. However, the package gnome-session-xsession is marked as deprecated, and the GNOME developers intend to drop support for X11 in the future.

Another planned task is the separation of the package gnome-classic-session, which includes extensions and settings for GNOME Shell to recreate the classic GNOME 2-style session. This package will still be installed by default, but support for X11 has been moved to a separate package called gnome-classic-session-x11, while the main package will maintain only support for Wayland-based sessions.

The main reason for deprecating X11 session support in Fedora is the decision to deprecate the X.Org server in RHEL 9 and remove it completely in the future major release of RHEL 10. Other factors contributing to the removal of introduction of support for Wayland in NVIDIA proprietary drivers and replacement of the fbdev drivers in Fedora 11 with the simpledrm driver, which works correctly with Wayland. Removing X36 session support will significantly reduce maintenance effort and free up resources to improve the quality of the modern graphics stack.

Moreover, Nor can we forget that in Fedora 41 the default use will be applied from the package manager DNF5, which has been delayed for several releases now and although complete parity in functionality with the old tools has not yet been achieved, the developers consider that the distribution is ready for migration, and that the missing features can be implemented later. For example, the transaction history management functionality behind the “dnf history” command is not yet available. Also working on integrating support for background processing dnf5daemon in the GNOME software application manager. The mechanism for upgrading the entire system to the next version (system upgrade command) requires additional testing.

At the time, DNF replaced the Yum package manager, which was written entirely in Python. The DNF5 project aims to unify existing low-level libraries, rewrite the remaining Python package management components in C++, and move core functionality into one library. libdnf5 separately, creating a wrapper around this library to hold the Python API.

Finally, if you are interested in being able to know more about it, you can consult the details in the following link


Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.