How do I enable Wayland?

K4LCIFER · 2021-12-31 03:56:27

I've had lots of trouble for quite some time now trying to get Wayland to work on my desktop. I really want to get wayland working so that I can mitigate the annoying quirks that come along with xorg, so I would greatly appreciate any help that I can get.

OS and DE: Arch Linux with Gnome
GPU and Driver: nvidia GTX 1080 with nvidia proprietary driver 495.46-6
Physical output: Dual Monitor setup with 1440p main monitor @ 144Hz and 1080p secondary monitor at 60Hz

Last edited by K4LCIFER (2021-12-31 04:00:07)

jasonwryan · 2021-12-31 04:04:30

https://wiki.archlinux.org/title/GNOME#Wayland_sessions

K4LCIFER · 2021-12-31 04:13:54

jasonwryan wrote:

https://wiki.archlinux.org/title/GNOME#Wayland_sessions

I'm not 100% sure exactly what you're wanting me to look at from the wiki page, but I tried what it said for gnome in the wayland sessions section by running

gnome-session --wayland

, but failed and outputted

mutter-Message: 20:11:02.962: Running GNOME Shell (using mutter 41.2) as a Wayland display server
Failed to setup: Could not take control: GDBus.Error:System.Error.EBUSY: Device or resource busy%

Last edited by K4LCIFER (2021-12-31 04:14:35)

yochananmarqos · 2021-12-31 04:38:21

Try creating a new user and see if it allows you to login to a Wayland session.

K4LCIFER · 2021-12-31 05:46:09

yochananmarqos wrote:

Try creating a new user and see if it allows you to login to a Wayland session.

Nope still no gear on the log in screen. I may just have to reinstall everything and go from there. There might be some strange config thats messing something up somewhere.

once · 2021-12-31 06:11:09

start from GDM.

jasonwryan · 2021-12-31 06:12:21

So you are logging in to your graphical session via GDM? That would explain why the manual start failed with the resource busy error.

Read your journal to see why GDM won't povide a wayland session.

K4LCIFER · 2021-12-31 06:42:20

jasonwryan wrote:

So you are logging in to your graphical session via GDM? That would explain why the manual start failed with the resource busy error.
Read your journal to see why GDM won't povide a wayland session.

grepping the output of journalctl for wayland yields a lot of occurences of

systemd[1008]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.

K4LCIFER · 2021-12-31 06:43:04

once wrote:

start from GDM.

what do you mean?

jasonwryan · 2021-12-31 07:25:28

K4LCIFER wrote:

grepping the output of journalctl for wayland yields a lot of occurences of
systemd[1008]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.

https://bbs.archlinux.org/viewtopic.php?id=57855

nkolew · 2021-12-31 08:18:03

Wayland is disabled on nvidia by a gdm udev rule.
You have to:
rm /etc/udev/rules.d/61-gdm.rules
and then
ln -s /dev/null /etc/udev/rules.d/61-gdm.rules

K4LCIFER · 2021-12-31 23:24:00

jasonwryan wrote:

K4LCIFER wrote:
grepping the output of journalctl for wayland yields a lot of occurences of
systemd[1008]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
https://bbs.archlinux.org/viewtopic.php?id=57855

That's all fine and good, but I have no idea what you specifically want me to give you. There's a lot of system logs.

K4LCIFER · 2021-12-31 23:25:20

nkolew wrote:

Wayland is disabled on nvidia by a gdm udev rule.
You have to:
rm /etc/udev/rules.d/61-gdm.rules
and then
ln -s /dev/null /etc/udev/rules.d/61-gdm.rules

That file is already empty for me. I't not linked to /dev/null, but it is empty.

Head_on_a_Stick · 2022-01-01 11:48:23

K4LCIFER wrote:

There's a lot of system logs.

That's why "$DEITY" invented pastebin sites

See also https://wiki.archlinux.org/title/List_o … ted_client but try to upload the logs from as brief a boot as possible.

K4LCIFER wrote:

That file is already empty for me

You shouldn't have any file at /etc/udev/rules.d/61-gdm.rules. The gdm package supplies the rule under /usr/lib/udev/rules.d/ (as do all other packages that ship udev rules)

What happens if you create a symlink to /dev/null from a file of the same name under /etc/udev/rules.d/?

NewJoarpa · 2022-01-01 15:27:56

So, I actually just solved this problem, you have to remove nvidia-egl-wayland or gdm will crash on wayland and start x11.
Make sure you are using nvidia drivers >= 495.

Here's more info:
egl-wayland GitHub Issue
Official nvidia forum

NewJoarpa · 2022-01-02 20:04:33

I found another better solution, downgrade egl-wayland to 1.1.7

It's better than using gbm which has a lot of performance issues using XWayland.

Last edited by NewJoarpa (2022-01-15 18:51:06)

Arch Linux

#1 2021-12-31 03:56:27

How do I enable Wayland?

#2 2021-12-31 04:04:30

Re: How do I enable Wayland?

#3 2021-12-31 04:13:54

Re: How do I enable Wayland?

#4 2021-12-31 04:38:21

Re: How do I enable Wayland?

#5 2021-12-31 05:46:09

Re: How do I enable Wayland?

#6 2021-12-31 06:11:09

Re: How do I enable Wayland?

#7 2021-12-31 06:12:21

Re: How do I enable Wayland?

#8 2021-12-31 06:42:20

Re: How do I enable Wayland?

#9 2021-12-31 06:43:04

Re: How do I enable Wayland?

#10 2021-12-31 07:25:28

Re: How do I enable Wayland?

#11 2021-12-31 08:18:03

Re: How do I enable Wayland?

#12 2021-12-31 23:24:00

Re: How do I enable Wayland?

#13 2021-12-31 23:25:20

Re: How do I enable Wayland?

#14 2022-01-01 11:48:23

Re: How do I enable Wayland?

#15 2022-01-01 15:27:56

Re: How do I enable Wayland?

#16 2022-01-02 20:04:33

Re: How do I enable Wayland?

Board footer