How to Fix Wayland GDM Issue in Fedora 22

Are you on Fedora 22 and puzzled by the fact that after you install you just can’t log in or do anything? Don’t worry! This is just a simple issue with Wayland (the next generation display server for Fedora).

Not everyone will encounter this issue inside GDM. This problem mostly appears with certain types of MacBooks. This problem isn’t just limited to MacBooks though. Other types of machines may run into this bug this as well.

If you do encounter a problem with the login screen, it can be quickly fixed. All that is required is a bit of poking around in a file. So how do you do it?

Note: you may need to add nomodeset to your grub boot parameters to get to TTY2 mode.

Before Wayland can be disabled for GDM, you’ll need to open a shell. Since the desktop manager isn’t working, we’ll need to gain access to the command line to fix the issue. You can enter this mode (TTY2) by pressing “Ctrl + Alt + F2” on your keyboard.

fedora-22-gdm-bug-tty2-mode-login-screen

Once you’ve pressed the right keyboard combination, you’ll see a message printed on the screen. This message will ask you for a username and password.

Enter your username and password, and then press the Enter key. Alternatively, you could use the root user and password. It really makes no difference.

With the user information entered, you will be dropped down to a basic command line terminal.

Gain root in the command line if you’ve decided to log in using your username.

From here we’ll need to open a text editor along with the file that needs to be edited. Use whatever terminal text editor you feel most comfortable with. For this guide we’ll be using Nano.

fedora-22-gdm-bug-open-grub-file-in-nano

Only one thing needs to be changed in this file for GDM to start working again. In the file you’ve opened with Nano, find WaylandEnable=false.

fedora-22-gdm-bug-nano-uncomment-and-edit-grub-file

When you’ve found WaylandEnable=false, you’ll need to uncomment it. Do this by removing the # from in front of it. This will turn Wayland off for GDM.

fedora-22-gdm-bug-save-edited-grub-file

After editing “custom.conf,” Wayland should be disabled. Just press “Ctrl + O” on your keyboard followed by pressing the Enter key to confirm and save the edits that you’ve made.

With the edits saved, exit nano and reboot the computer. By the next boot, the Wayland issue will be completely fixed in GDM, and you’ll be able to use Fedora 22.

Fedora is a great distribution where a lot of innovation happens in the Linux space. Fedora is often the first to try out and implement new things. This is usually a great thing as it allows Fedora fans the ability to try out new stuff before anyone else in the Linux community gets their hands on it.

Sometimes, though, this can be a painful thing. There’s a reason why the Fedora operating system is often referred to as “beta software.” Obviously Wayland is still a new thing, and that’s why issues like this graphics bug might come up.

Luckily, Fedora is Linux; we can tear it apart and fix things on our own. I hope that this simple guide has helped you bypass a small, but annoying, issue.

What are the worst bugs you’ve encountered in Fedora? Let us know in the comments below!

7 comments

    • Bill

      To be fair the article is titled. “How to fix Wayland GDM ISSUE”
      His title if read correctly does not imply in any way that he is making wayland work in this article.

      Disabling wayland is a FIX for the ISSUE.

      Do not criticize a good article because you did not comprehend the title.

  1. Have similar issue but the custom.conf doesn’t contain any entry with Wayland in my Fedora 22.
    Can logi with external monitor, the laptop screen doesn’t work with 4.xxx kermel, only when I select the old 3.xxx kernel in grub.

    Or does the custom.conf change content after the login?
    Thanks for help, E335

  2. Thanks, disabled, my cpu is no longer pegged, this allows me to do some work in the linux image (F22 Distro in VMWare Player 7 in Windows 10) while brains bigger than mind figure out what the issue is.

  3. Thank you thank you. I run mostly server stuff and just want a reliable GDM for when I occasionally need it.

  4. Thanks for the workaround, Derrik. I got hit with Wayland continually crashing after I installed Fedora 22. Happy to have Wayland gone!

  5. What can I use instead of nano? When I try it it gives me this error:


    bash: nano: command not found…
    install package ‘nano’ to provide command ‘nano’? [N/y]

    After that I try to install nano and I get this error:

    *Downloading packages… Failed to install packages: cannot download n/nano-2.3.4-6.fc21.i686.rpm to /var/cache/PackageKit/metadata/updates/packages/: cannot download n/nano-2.3.4-6.fc21.i686.rpm: All mirrors were tried

    Is there anything tat I can do to fix this?

Comments are closed.

Sponsored Stories