Fedora Wayland Not Starting: Diagnostic Guide for Quick Fixes

Problem

After a fresh Fedora install or a system upgrade, the graphical login fails to launch. The screen freezes, shows an error such as "Wayland: Unable to load NVIDIA driver," or GDM only offers an Xorg session. This guide helps you pinpoint the cause and apply the right fix.

Recognizable Symptoms

• Login prompt disappears and the system reboots or drops to a TTY.
• GDM shows only "GNOME on Xorg" even though Wayland is enabled in config.
• Error messages: Wayland: Unable to load NVIDIA driver, Failed to load libdrm, or generic “No display”.
• System boots to a console; GDM never starts.

Common Causes Table

Ordered Diagnostic Checks

1. Check GDM configuration

   # Run as root or with sudo
   cat /etc/gdm/custom.conf | grep WaylandEnable

   Expected output: WaylandEnable=true. If missing or set to false, edit the file and set it to true (under the [daemon] section). Remember to back up the file first: sudo cp /etc/gdm/custom.conf /etc/gdm/custom.conf.bak.

2. Inspect system logs for Wayland or GPU errors

   # From a terminal or TTY
   journalctl -b | grep -i wayland
   journalctl -b | grep -i nvidia
   

   Look for lines like Failed to load libdrm or Wayland: Unable to load NVIDIA driver. These clues point to the underlying issue.

3. Verify GPU driver status

   # List installed NVIDIA packages
   rpm -qa | grep nvidia
   

   If you see nvidia-driver but not nvidia-driver-libs or the driver lacks Wayland support, consider switching to the open‑source nouveau driver or installing the latest nvidia-driver from the RPM Fusion repository.

4. Confirm Mesa and libdrm packages

   # List Mesa DRI drivers
   rpm -qa | grep mesa-dri-drivers
   # List libdrm package
   rpm -qa | grep libdrm
   

   Missing packages trigger “No display” errors. Install them with: sudo dnf install mesa-dri-drivers libdrm. After installation, reboot.

5. Check systemd‑display‑manager status

   # Verify GDM service is enabled and active
   systemctl status gdm.service
   

   If the unit is masked, inactive, or failed, enable it: sudo systemctl enable --now gdm.service. If the service is missing, reinstall GDM: sudo dnf reinstall gdm.

Fixes Tied to Findings

• Enable Wayland in GDM: Edit /etc/gdm/custom.conf to include [daemon] and WaylandEnable=true.
• Switch NVIDIA driver: Remove legacy driver (sudo dnf remove nvidia-driver) and install the latest from RPM Fusion (sudo dnf install nvidia-driver). Reboot.
• Install missing Mesa/libdrm: sudo dnf install mesa-dri-drivers libdrm and reboot.
• Re‑enable GDM: sudo systemctl enable --now gdm.service or reinstall if corrupted.

Escalation Criteria

If after performing all checks and fixes Wayland still does not start, consider:

• Reviewing /var/log/Xorg.0.log and journalctl -b for additional error messages.
• Testing with a different user account to rule out per‑user configuration issues.
• Running sudo dnf update to ensure all packages are current.
• Consulting Fedora’s bug tracker or community forums with the collected logs. Provide the output of the diagnostic commands above for context.

In rare cases, a kernel bug or hardware incompatibility may be the root cause. If you suspect this, file a bug against the Fedora kernel or the specific hardware vendor.