You want a traditional desktop without wiping your system
You spent months building a workflow around GNOME, then realized the gesture navigation drains your laptop battery faster than expected. Or maybe you inherited a Fedora machine that feels too heavy for its hardware. You want separate panels, a right-click context menu that actually makes sense, and a window manager that respects your muscle memory. MATE is the direct continuation of GNOME 2, and installing it on Fedora is straightforward. You do not need to format your drive or reinstall. You just need to add the package group and tell the display manager to hand you the right session.
What is actually happening
Fedora ships with GNOME as the default desktop environment. The package manager treats entire desktop environments as installable groups rather than single packages. When you request a desktop group, dnf pulls the core window manager, panel applets, file manager, terminal emulator, and a curated set of recommended utilities. The display manager, usually GDM on Fedora Workstation, reads available session files from /usr/share/wayland-sessions/ and /usr/share/xsessions/. Adding MATE simply drops new .desktop files into those directories. Your existing GNOME installation remains untouched.
The two environments share underlying libraries like GTK, systemd, and NetworkManager. That shared foundation is why the installation is fast and why configuration drift rarely breaks either side. Fedora packages desktop environments as modular groups so you can swap or run multiple environments on the same system. The package manager tracks group membership separately from individual package ownership. This means you can update MATE without touching GNOME, and you can remove the group later without orphaning your system.
Convention aside: dnf groupinstall is the correct tool for desktop environments. dnf install works for individual applications. Mixing the two leads to partial installations and broken session files. Stick to groups for environments, and individual packages for utilities.
The fix
Run the group install command. Fedora's official repository maintains the @mate-desktop-environment group, which pulls everything you need without dragging in conflicting GNOME-specific tools.
sudo dnf groupinstall "MATE Desktop Environment"
# WHY: groupinstall pulls the curated set of packages defined by the MATE group
# WHY: sudo elevates privileges so dnf can write to /usr and /etc
# WHY: quotes around the group name prevent shell expansion issues with spaces
If dnf reports a dependency conflict, it usually means a GNOME-exclusive package is holding a slot that MATE wants to fill. The package manager will suggest removing the conflicting package. Review the list carefully. If it only mentions GNOME-specific utilities like gnome-terminal or nautilus, approve the removal. MATE ships with mate-terminal and caja as direct replacements. The transaction will complete safely.
After the transaction completes, log out of your current session. Do not reboot yet. The display manager needs to reload its session list, and a simple logout forces that refresh without touching your running services. Rebooting is unnecessary and wastes time.
At the login screen, look for the session selector. On GDM, it sits in the bottom-right corner as a gear icon or a dropdown menu. Click it and choose MATE or MATE (Software Rendering) if you are on a machine with broken GPU drivers. Enter your password and press Enter. The system will load the MATE panel, the window manager, and your configured autostart applications.
Verify it worked
Check that the session actually loaded and that the package group is registered correctly. You need to confirm both the runtime environment and the package manager state.
echo $XDG_CURRENT_DESKTOP
# WHY: prints the active desktop environment identifier
# WHY: confirms the session manager recognized MATE as the running environment
# WHY: should output MATE if the login succeeded
dnf group list --installed | grep -i mate
# WHY: lists all installed package groups
# WHY: filters the output to verify the MATE group is tracked
# WHY: helps you later if you need to remove or update the environment cleanly
Open a terminal and run htop or btop. Compare the memory footprint to your previous GNOME session. MATE typically uses less RAM because it avoids the heavy compositor and shell extensions that GNOME relies on. If the panels are missing or the theme looks broken, your user configuration directory might be holding onto stale GNOME settings. Clear the cache and restart the session.
Run journalctl -xe after login. The x flag adds explanatory text and the e flag jumps to the end. Most sysadmins type journalctl -xeu <unit> muscle-memory style. Scan for mate-panel or mate-session warnings. If you see missing plugin errors, install the specific applet package rather than reinstalling the whole group.
Common pitfalls and what the error looks like
The most common issue is a missing network manager applet. MATE uses mate-network-manager-applet, but if you previously configured NetworkManager through GNOME settings, the applet might not appear in the panel. Right-click the panel, select Add to Panel, and search for NetworkManager. If it does not show up, install it explicitly.
sudo dnf install mate-network-manager-applet
# WHY: ensures the panel applet is present even if the group install skipped it
# WHY: prevents the "no network icon" confusion after first login
# WHY: runs as a standalone package install to avoid group dependency resolution
Another frequent problem is theme and icon pack mismatches. MATE expects GTK2 and GTK3 themes in ~/.themes/ and ~/.icons/. If you copied a GNOME theme that only supports GTK4, the controls will render with missing borders or broken spacing. Stick to themes that explicitly list MATE or GTK3 compatibility. Config files in /etc/ are user-modified. Files in /usr/lib/ ship with the package. Edit /etc/. Never edit /usr/lib/.
You might also encounter a black screen after selecting MATE. This usually means the display manager is trying to start a Wayland session that your GPU driver does not support. Switch to the X11 fallback by selecting MATE (Software Rendering) or MATE on X11. If the black screen persists, check the display manager logs.
journalctl -xeu gdm
# WHY: pulls recent logs for the GDM service
# WHY: the x flag adds explanatory context to each log line
# WHY: the e flag jumps to the end so you see the latest failure
Look for Failed to initialize Wayland compositor or X server terminated. The log will tell you whether the issue is a missing driver, a permission problem, or a corrupted session file. SELinux denials show up in journalctl -t setroubleshoot with a one-line summary. Read those before disabling SELinux. A botched upgrade can leave you unable to boot. Run this from a backup VM first if you can.
Reboot before you debug. Half the time the symptom is gone.
When to use this vs alternatives
Fedora gives you several desktop environments, each optimized for different workflows. Pick the one that matches your hardware and your tolerance for configuration.
Use MATE when you want a stable, traditional desktop that respects your muscle memory and runs comfortably on older hardware. Use GNOME when you prefer a gesture-driven workflow, built-in accessibility features, and tight integration with modern Wayland compositors. Use KDE Plasma when you need granular control over every pixel, animation, and system setting without touching configuration files. Use XFCE when you want the lightest possible footprint and do not mind a more utilitarian interface. Stay on the default GNOME if you only deviate from the defaults occasionally and want the most tested experience on Fedora Workstation.
Trust the package manager. Manual file edits drift, snapshots stay.