This page is to be treated as a work-in-progress (WIP) as Mageia 9 has NOT been released yet.
Mageia (from Greek μαγεία (mageía) - magic, enchantment) is a free and open-source operating system from the GNU/Linux family of operating systems. Mageia is developed by a community of dedicated users, and backed by the non-profit organisation mageia.org – a group of individuals elected by the Mageia Board. Whether you're a first-time GNU/Linux user, a software developer, an experienced system administrator or a casual web-surfer, Mageia is the right choice for you. Mageia can be installed on a computer as both the main operating system and an alternative to one or several other installed operating systems.
The release date of the upcoming stable release of the Mageia project – Mageia 9 – is still to be announced.
Mageia can be installed using one of three installation media:
All ISO images can be burned to a CD/DVD or a USB flash drive. Note: Due to the actual capacity of drives being slightly lower than the marketed size, a 4 GB ISO image could be too big for some nominally-4 GB drives.
The different download options can be found on the Mageia 9 download page. Both direct (FTP and HTTP) and BitTorrent downloads are available.
For more information, have a look at our installation media manual page.
The software packages that are included in Mageia reside in three different repositories (collections), depending on the type of licence applied to each package. Here is an overview of these repositories:
The Non-free software collection is enabled by default in the installer, but can be disabled if necessary.
The Tainted software collection is available but disabled by default, i.e., it's completely opt-in. It is a good idea to verify your region's laws before using packages from this repository.
32-bit repositories are configured, but disabled by default on 64-bit systems. Some 64-bit programs such as Steam require dependencies found in 32-bit repositories. Therefore, if you would like to install software which depends on 32-bit packages, make sure that you have the "Core 32-bit Release" and "Core 32-bit Updates" package collections enabled in RPMDrake. Likewise, some 64-bit packages from the Non-free or Tainted package collections could depend on 32-bit packages from their respective collections. Thus, it is strongly recommended to always enable repositories in pairs (32-bit together with 64-bit) so as to not encounter issues while updating.
Urpmi metadata are compressed with Zstd instead of Xz, resulting in faster parsing.
Most python2 modules & software were removed.
The ARM (Advanced RISC (Reduced Instruction Set Computing) Machine) port rebooted during Mageia 8 days has been enhanced. The core is available for ARMv7 and AArch64.
There is no traditional installer for now, and it is still considered experimental, but most of the distribution was built successfully on both architectures (see our ARM status overview for details). The plan is to provide installation images for popular ARM devices in the coming months. There is no ETA for those as of Mageia 9's release.
Drakboot is now somewhat able to set up UEFI on AArch64.
The rescue system has been enhanced:
New translations have been added, while others were improved. Thank you to our dedicated community of translators for your reliable work.
RPM has been upgraded to version 4.17.
RPM 4.17 offers key improvements to RPM as a whole, including:
More information on changes from RPM 4.16 (which shipped with Mageia 8) to RPM 4.17 is available from the RPM website:
DNF (Dandified Yum) was introduced as an alternative to urpmi since Mageia 6.
DNF is a next-generation dependency resolver and high-level package management tool that traces its ancestry to two projects: Fedora's YUM (Yellowdog Updater, Modified) and openSUSE's SAT Solver (libsolv). DNF was forked from YUM several years ago in order to rewrite it to use the SAT Solver library from openSUSE and to massively restructure the codebase so that a sane API would be available for both extending DNF (via plugins and hooks) and building applications on top of it (such as graphical frontends and system lifecycle automation frameworks).
DNF comes with enhanced problem reporting, advanced tracking of weak dependencies, support for rich dependencies (see the RPM release notes for more on this), and more detailed transaction information while performing actions.
Mageia 9 ships with DNF v4.6.0.
System upgrades using DNF are supported. See the section on upgrading with DNF in the release notes for more information.
More information on modularity: https://docs.pagure.org/modularity/
DNF release notes: https://dnf.readthedocs.io/en/latest/release_notes.html
With fresh installations via the classical and live media, DNF will be installed in parallel with urpmi. Depending on the method used to upgrade to Mageia 9, it may be necessary to install the dnf package to have it available.
For information on how to use DNF, please refer to the wiki page: Using DNF.
Our RPM-MD (RPM MetaData) repositories (used by DNF and PackageKit) provide AppStream metadata. Tools like GNOME Software (GNOME Desktop, packaged as gnome-software) and Plasma Discover (KDE Plasma Desktop, packaged as discover) leverage AppStream metadata to provide a rich experience when searching, identifying, and managing applications.
AppStream is a cross-distribution effort for enhancing software repositories by standardizing software component metadata. It enables an application-centric view on package repositories and provides specifications for things needed to create user-friendly application centers.
See the AppStream website for more information: https://www.freedesktop.org/wiki/Distributions/AppStream/
The 'Welcome' screen is an application that is presented to users when booting into a fresh installation of Mageia. It has now been entirely reworked to have a linear approach, with successive steps following in a logical order of important things to know and do post-installation. By default, it will run at each subsequent boot, but this behaviour is optional. Even if the auto-run option is disabled - it can be invoked at any time as an application (mageiawelcome).
Isodumper is a tool to write ISO images on memory devices. The checking routine after writing operations is looking now for a sha3 sum file and corresponding signature.
The added persistence partition can now also be encrypted. This will be recognized only for Mageia 8 and later ISO images. See here for more information.
The Docker ecosystem has been augmented (based on the 19.03 version of the engine) with many additional tools such as docker-compose (orchestration with v3 support), containered (daemon controlling runC), docker-registry (share of images), docker-machine (install docker on a remote system), and python-docker (python 2 and 3 libraries for engine API management).
With Mageia 9, the LiveCD Tools have been rebased to the latest version (v27.0).
For information on how to use the LiveCD Tools, please refer to the wiki page: Using the LiveCD Tools
The GUI mode has been enhanced to include the summary stage from the classical installer, allowing easy configuration of locales, timezones, system services, and firewalls. The individual package selection stage now includes a flat list mode, removing the restrictions on what packages can be selected.
For more information, please refer to the wiki page: draklive2
This is a fork and major rewrite of the Memtest86+ memory test utility. Unlike Memtest86+, PCMemTest can be used with UEFI as well as with legacy BIOS boot (with the limitation that with UEFI boot, keyboard input only works if the CSM is enabled in the BIOS). PCMemTest replaces Memtest86+ as the memory test utility on all the Mageia ISOs. It may also be installed in a user's system, where it will be automatically added to the system boot menu.
All hardware managed by this kernel version is enabled. The kernel provides better graphics with Mesa 21.2.
Mesa has been updated to Mesa 21.2.3.
Mageia 9 ships with X.Org 21.1. XWayland 21.1.2 has been split from the Xserver and is packaged as standalone tool for easier maintenance.
NVIDIA's proprietary drivers are provided in the nonfree repositories:
Some laptops comes with "Hybrid Graphics", meaning they have two GPU: one is usually "internal" (or "integrated") into the CPU, and is called IGP (Integrated Graphic Processor), and the other is "dedicated", external to the CPU, and it is called "discrete" (DGP, Discrete/Dedicated Graphics Processor). The integrated is power efficient, while the discrete is faster.
Owners of NVIDIA Optimus laptops (integrated Intel or AMD/ATI CPU+GPU, plus a discrete NVIDIA GPU) now have three ways to benefit from the power of their NVIDIA GPU:
In all three cases, when configuring the graphics drivers, one must during install and the usual Mageia tools configure only the integrated GPU (at least in most Optimus configurations), as it is typically the only one physically connected to a monitor. (If failing, try the other way around.)
All the desktop environments mentioned below are included in Mageia's online repositories, and can be installed in parallel on any Mageia 9 system. Some of them are also included on the physical media, LiveDVDs and Classical DVDs, as specified in each section.
Plasma, the desktop environment from the KDE community, is provided as version 5.21.4, built on top of Qt 5.15.2 and KDE Frameworks 5.81 and with KDE Applications 20.12.3.
If you want to try Plasma under Wayland, install plasma-workspace-wayland, and it should appear in your favourite display manager's list of desktop environments at log in.
Note also that Wayland session with Nvidia's 460 (current) nonfree-drivers is available by making sure that "nokmsboot" is removed and "nouveau.modeset=0" is passed to Kernel command line. - This is provided as Technology Preview for testers.
The default display manager (DM) for the Plasma environment is the Simple Desktop Display Manager (SDDM).
If you have Compiz enabled in Mageia 8, disable it before upgrade, see Errata.
Plasma has a specific 64-bit LiveDVD and it can also be installed from the Classical DVD ISO (traditional installer).
GNOME 40.4 is provided. It now defaults to running on Wayland, but also provides an alternative "GNOME on Xorg" session. Note that with Nvidia's nonfree drivers, GNOME defaults to start an X11 session.
For those preferring the GNOME 2 look and feel, GNOME 3 also provides a "Gnome Classic" session.
GNOME has a specific 64-bit LiveDVD and it can also be installed from the Classical DVD ISO (traditional installer).
The very lightweight GTK+2-based desktop environment is still available and continues to receive improvements from upstream and our Mageia maintainer, even though its community has partly refocused on LXQt.
LXDE can be installed from the Classical DVD ISO (traditional installer).
Xfce 4.16 is provided.
Xfce has dedicated 32-bit and 64-bit LiveDVDs and it can also be installed from the Classical DVD ISO (traditional installer).
LXQt 0.17.0 is provided.
LXQt cannot be installed out of the box from the Classical DVD ISO (traditional installer) due to space constraints on the ISOs. Online media need to be added to enable more options during the initial installation - this is explained in the installer documentation (Note: use documentation for release 8 until the new one is ready). As transparency compositor in combination with openbox, picom replaces compton - may need manual adjustment.
MATE 1.26.0 is provided.
MATE can be installed from the Classical DVD ISO (traditional installer). Due to DVD space considerations, some applications such as mate-screenshot (screenshot application) are not included in Classical DVD ISO. For a full MATE Desktop experience, users are advised to install task-mate package after initial installation.
Cinnamon 5.0.0 is provided.
Cinnamon can be installed from the Classical DVD ISO (traditional installer).
The Enlightenment task package comes with E24.2 and Enlightenment Foundation Libraries (EFL) 1.25.1 -- including the Elementary, Evas-generic-loaders and Evas-generic-players packages. Among the highlights of this version is Bluez5 support, an improved screenshot tool, a more flexible music control module, the Evisum system monitor, the now integrated Polkit-EFL authentication agent, and a separate configuration for applications to be loaded when restarting E. For more details on this version, see https://www.enlightenment.org/news/e24.2.
Of course, Mageia includes E's Econnman UI for the connman connection manager, along with three EFL-based applications: the Terminology advanced terminal emulator, the nimble Ephoto image viewer, and the light-weight Rage video player. As with the prior release, Mageia 9 also offers a Mageia-branded theme as the default.
For those new or returning to E, startup applications and processes (such as the Mageia Online Applet for update notifications) are not automatically picked up from /etc/xdg/autostart, but are enabled at startup by going to Main menu > Settings > Apps > Startup Applications and adding the desired applications and system processes. Applications (only) to be loaded on restarting the DE are handled separately from a list available via Main menu > Settings > Apps > Restart Applications.
Enlightenment's system tray, which uses SNI appindicator notifications, is a separate module that must be loaded (Main menu > Settings > Modules) and added to a shelf (panel), where the Mageia Online Applet and Netapplet will be displayed (when enabled) along with others. Gtk applications with appindicators (e.g., Ubuntu indicator plugin for Pidgin) now have their icons correctly displayed as well.
Currently, there are two known issues. First, Mageia enables systemd-networkd to manage networking by default. Those who prefer to use connman with the Econnman interface may find it is not always functional (after disabling systemd-networkd and enabling connman.service), perhaps as a result of the default wpa_supplicant configuration. (There is a separate, recently-developed wireless gadget for managing multiple network backends that is not yet included in the Mageia repositories.) Second, restarting E sometimes results in a warning that the Efreet cache was not updated. In general, this can be ignored as it results from a time-out which still seems to be too short for some systems.
You can also keep your Mageia 9 installation even more lightweight, and we provide for this a plethora of small and efficient window managers. You can find afterstep, awesome, dwm, fluxbox, fvwm2, fvwm-crystal, i3, icewm, jwm, matchbox, openbox, pekwm, sugar, swm, and windowmaker. After installation, they appear in the login menu of your display manager.
IceWM is installed by default as a backup desktop environment even if you select Plasma or GNOME in the installer. It is also present in all Live ISOs.
To launch it you select "icewm-session" in the login menu of your display manager.
LibreOffice has been updated to 7.1.2. See official release notes for details.
Iceape is dropped, because Seamonkey has not yet been ported to python 3. Note: You need to export content before upgrading Mageia! For some guiding see mga#26593#c14 and also search internet.
Since the last patent expired in April, 2017, mp3 encoding is now available in the core media. Tainted media are still needed for H.264, H.265/HEVC and AAC encoding.
In the Mageia community, our love for free software extends to open source games. A huge effort has been made during the Mageia 9 release cycle to package many new games, making Mageia 9 a very good platform for intensive and casual gamers alike. You can check the Mageia App DB to see a list of all the new and updated games in Mageia 9. The following section will only give some cherry-picked examples for each game category.
Mageia 9 comes with gcompris-qt 1.0 which brings some new activities. We were  among the donors in February, 2015, to improve the graphical interface of this very important project.
Glibc has been updated to 2.34. GCC has been updated to 11.2, GDB to 10.2 and Valgrind to 3.17. LLVM has been updated to 12.0.1.
Firebird has been updated to 4.0.0
IPython has been updated to 7.22.
Most libraries were updated to recent stable versions (long-term support when available), such as Qt 5.15.2 and GTK+ 3.24.30. GTK4 is also provided at version 4.2.1 Tcl/Tk is at version 8.6.11.
Ocaml has been updated to 4.13.1
Java stack has been updated to 11, java 8 is still available but is not the default.
Mono has been updated to 6.12.
The MinGW stack has been updated.
QEmu has been updated to 6.1.
libvirt has been updated to 7.6, virt-manager to 3.2.0, libguestfs to 1.45.4. Some of libguestfs subpackages are now built from guestfs-tools 1.46.0
Xen is at version 4.15.0.
VirtualBox is at version 6.1.26.
Note: In 6.1 series, VirtualBox only supports x86_64 hosts. An existing 32 bit host will be removed!
Python 3 has been updated to 3.9.4. Python 2 is being retired (most python2 modules have already been removed).
Perl has been updated to 5.34.0.
Ruby has been updated to 2.7.2.
Rust is at version 1.51.0. It will be updated during Mageia 9's support life to follow new developments.
PHP has been updated to 8.0.3, which gives a further performance improvement.
New installation of nginx http server uses "apache" user: Web servers in Mageia are supposed to use the "apache" user created by the webserver-base package (which they then need to require). This package no longer use a "nginx" user, fixing mga#26183.
At release Mageia 9 had no Nextcloud server packaged, because version 21 - the first supporting PHP8 - was not released yet.
On the positive side we provide two paths:
Mageia 8 came with Nextcloud 15 in core release repository. The Nextcloud installation must not skip a major version! Therefore *before* upgrading to Mageia 9, you have to update Nextcloud first to version 16, then to 17, then to 18, then to 19, then to 20. You find these versions in Mageia 8 backports repository. For each update also make sure you have apps updated (they are updated by using Nextcloud interface) and some are better disabled or uninstalled before each update, then enabled after each, and also verify Nextcloud including all apps works after each update, check logs. Before starting the process it is a very good idea to take backups. Also, see evolving instructions at Nextcloud.
Upgrading from Mageia 8 is supported, and has been fine-tuned over the past few months.
- In these cases, you have to do a fresh installation. (possibly keeping the /home directory)
The Mageia Update notification applet, Mageia Online, will notify you that a new Mageia release is available, and ask if you wish to upgrade. If you agree, the upgrade will be carried out from within your Mageia installation without any further steps being necessary.
If you have disabled the applet, or it is not automatically running for some reason, you can upgrade manually either using the GUI (mgaonline) or the CLI (urpmi/dnf system-upgrade). Each method is outlined below.
Fully update your system and check you have enough free space before starting the upgrade. At least 2 GB, depending on your configuration - see Note and safe method at Upgrading online, using urpmi (CLI) below.
- If it does not offer the upgrade:
After a reboot, the blue upgrade icon should appear when Mageia Online next checks for updates. - If Mageia 8 has reached EOL, it will be orange and show a pop-up warning that Mageia 8 is no longer supported.
Alternatively, you can launch the upgrade process by entering the following in a terminal:
It will notify you of the availability of the new Mageia 9 distribution, configure Mageia media sources and start the migration.
This method is useful when the root partition is encrypted as the booted system is already decrypting the partition.
There are multiple ways of getting a Command Line Interface (CLI).
The best method for performing an upgrade is to use run-level 3 so that the X server and graphical environment is not running.
Therefore, the upgrade should be cleaner using run-level 3 than using a terminal application as fewer programs are running which could potentially mess up the upgrade.
If you have dnf installed, you will have to stop the dnf makecache timer, because it causes a crash of urpmi when run during the upgrade. The commands are included below. See mga#25072.
Run-level 3 can be enabled by appending "3" to the kernel command line by editing it at boot and to get then a login prompt. Other option is to use the command: systemctl isolate multi-user.target
It is recommended to run "script upgrade_log.txt" before launching the next commands to capture the upgrade messages just in case a failure occurs. The messages will be written in upgrade_log.txt file. Use "exit" to quit out of "script".
Here are the general upgrade steps:
If you're using (or now change to use) DNF for software management (configured appropriately per our wiki page on using DNF), you can upgrade Mageia in just a few steps. Note all commands must be run as root.
Now enjoy some beverage while looking at the bubbles on our boot splash - and above it, messages what is happening. When done, it will reboot to let you enjoy your new Mageia.
You can use the traditional (so, non-Live) Mageia 9 DVD to do clean installs, but also to upgrade from Mageia 8.
It is recommended that the online repositories be set up during the upgrade as the DVD only includes a subset of the complete set of Mageia online repositories. This is especially important if you use important 32-bit packages in an otherwise 64-bit install, because the 64-bit ISO will only contain the 64-bit packages, so the upgrade is likely to fail if you do not add online repositories.
Moreover, it is possible that a particular Mageia 8 installation may have received an update to a later version of software than that available on the ISO. When this happens, an upgrade may fail to complete. At the time the ISOs are tested, it is impossible to anticipate which Mageia 8 packages may be updated in the future, so offline upgrades (i.e., upgrades attempted without setting up the online repositories) are not supported.
On the first reboot, use the command 'urpmi --auto-update' to make sure all packages were updated.
Firstly, on the running Mageia 8 system:
Then prepare and boot the traditional installer as described above, and:
User actions needed that are not described elsewhere on this page nor in Errata.
See the Errata page.
We have a bug tracker. Before reporting any bugs, please read the Errata and also search the bug tracker to see if the issue is already reported. - If it is, then maybe you can add valuable information, or help testing a proposed update. To contribute, you need a Mageia account, which you can create at https://identity.mageia.org/. If you don't know, see how to report a bug.
You are also welcome to our Forum. For the development phase visit the section "Testing : Alpha, Beta, RC and Cauldron".
The following packages have been removed from the distribution. They won't be affected by the upgrade process, they should continue to work, but won't receive any support anymore if they don't. Moreover, they won't receive any updates anymore, which means they are likely to get outdated from upstream versions first, and potentially get exposed to security issues second. You should probably switch to an upstream version, but that's your own decision.
The category contains the following packages:
The following packages have been removed from the distribution and marked as obsolete in the task-obsolete package: they will be removed by the upgrade process.
This category contains the following packages, alphabetically: