July 1, 2025
This document explains how to install x86_64 Wine on AMD64 Mageia Linux. x86_64 Wine can run both 64-bit and 32-bit Windows apps.
Mageia offers only Wine Stable. Wine Development and Wine Staging are not available. At the time of this writing, the version of Wine that is installed is Wine 8.0.
Throughout this procedure, you will need to issue Terminal commands as root. If you know you are already authorized to use sudo, you can continue here. Otherwise, go to the Appendix on Sudo at the end of this document and enable sudo for yourself.
References
Enabling Repositories with dnf
An installation of x86_64 Wine supports both 64-bit and 32-bit Windows apps. In Mageia, 64-bit core and update repositories are enabled by default, but the 32-bit repositories are not, so, before installing Wine, the 32-bit core and update repositories must be enabled.
Open a Terminal window and execute these commands.
$ sudo dnf config-manager --set-enabled mageia-i586
$ sudo dnf config-manager --set-enabled updates-i586
The next command synchronizes the repositories.
$ sudo dnf distro-sync --refresh
The output of the previous command must contain these four repositories.
Mageia 9 - i586
Mageia 9 - i586 – Updates
Mageia 9 - i86_64
Mageia 9 - i86_64 – Updates
Two graphics libraries,
$ sudo dnf install libmesagl1 libmesaglu1
and a library for manipulating JPEG image files.
$ sudo dnf install libjpeg8
$ sudo dnf install wine64 wine32
Open a Terminal window and execute
$ wine --version
The next section configures Wine with the command $ wine winecfg. After executing that command, I encountered difficulty in getting buttons in the configuration panel to respond, something I have never seen in any other installation of Wine. I always did get buttons to respond, but I cannot offer a recipe that always worked. A random click in the open panel area and doing a lengthy click (hold the left mouse button down for several seconds) seemed to help.
Though irritating, this did not affect functionality.
Remote file
content-configure-test-windowsapps.html
does not exist.
Reference
To see if you are authorized to use sudo, open a Terminal window and execute the following command.
$ sudo echo Hello
If Hello is displayed, you are authorized to use sudo, so can proceed to Enable 32-bit repositories. Otherwise, continue here.
If the result of the command was that sudo is an unknown command, it must be installed. If that is necessary, execute
$ su
# urpmi sudo
Return to being a normal user.
# exit
Close the Terminal window.
If you did install sudo, you must reboot your computer before continuing.
Continue by configuring sudo.
The following adds the wheel group to the sudo configuration file. (In case the name 01wheel fails, or you don't like it, just replace it with something else.)
$ su
# echo "%wheel ALL=(ALL:ALL) ALL" > /etc/sudoers.d/01wheel && chmod 440 /etc/sudoers.d/01wheel
Use nano or any other command line editor to open /etc/group for editing.
# nano /etc/group
Locate the line
wheel:x:10:
and change it to
wheel:x:10:name
but replace name by your login name.
Exit from Nano and reboot your computer.
After the reboot, you can execute
$ sudo echo Hello
to verify that you really can use sudo.
Did you find this page helpful? Have constructive feedback? Wisdom to share?
Send email to Email Address
