Numerous Issues w/ Wayland

WannabeWayland · 2023-11-21 23:30:31

Hello all,

I've been having numerous issues with Wayland. The most pressing issue would be that Wayland occasionally freezes.

When frozen, pressing the caps lock key doesn't cause it to light up. Pressing Ctrl+Alt+F2 to switch to TTY does nothing.

I'm running stock dwl as my compositor on an AMD Ryzen 5 PRO 5650U CPU.

Besides this, Firefox doesn't work on Wayland. Firefox launches and doesn't usually complain (output any messages to stdout), but appears to wait forever, even with the MOZ_ENABLE_WAYLAND environment variable set. Without the variable, Firefox closes instantly. Chromium works just fine, although it does launch under XWayland by default, not sure if that could indicate something. I do remember that when I ran Firefox under GDB in an attempt to locate cause of the infinite, I stopped the program on a call to poll(). If needed, I can run strace to give a more detailed

For my terminal I'm running the foot server with connecting clients. This brings up another issues that may or may not be related to foot. Sometimes when I launched Firefox, the terminal would output that some environment variable had been overridden. This would cause some kind of notification noise to occur. Is this truly happening, does my mysterious notification noise exist? If so how can I get rid of it.

I do see that Wayland, in the past, had stability variations between GPUs, given I'm running under an iGPU, does this cause issue?
Is Wayland just not ready yet?

The command journalctl -k -b -1 yields 1 line that may be of interest:

Nov 21 14:39:17 laptop kernel: Xwayland[1397]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set

Zod · 2023-11-22 00:08:22

Not much help but..

It sounds like you are trying to run wayland using proprietary drivers that do not (fully) support it.

In my case it was nvidia 390xx...I had much better results with nouveau.

Someone might be able to help but they will need to know what GPUs you have and what drivers your attempting to use.

Trilby · 2023-11-22 00:45:51

Please be specific. You do not run wayland, you run a wayland compositor: which one?

If you think the message about "some environment variable" is relevant, then please post the actual message / environment variable.

As for the GPU issue, I'm not sure what you are referring to. Support for NVIDIA lagged a bit for some compositors. But is this relevant? Do you have a NVIDIA gpu, or what?

WannabeWayland · 2023-11-22 01:26:51

I specified that I was running under stock dwl. I also specified I was running under an AMD iGPU. I am running under the open source drivers. I was wondering if it might be because of the integrated GPU, I certainly hope it is as it'd be a lot less of a mysterious failure then.

My system is fully updated.

If someone could provide some knowledge about possible locations for the problem, I'd be very thankful. I'm not sure what handles ctrl-alt-fx TTY switches, nor what handles the caps locks lighting up. If they occur at some low level then I have a grand problem. If they don't, and it's dwl's issue, then it's a simple fix.

The environment variable override would be:

ATTENTION: default value of option mesa_glthread overridden by environment.

Lone_Wolf · 2023-11-22 12:43:24

The gl threading message is normal for specific applications (firefox is one of them) and should be harmless.

You are using https://aur.archlinux.org/packages/dwl/ ?

Have you tried with other wayland compositors to verify if your issues are dwl-specific ?

Last edited by Lone_Wolf (2023-11-22 12:44:40)

Arch Linux

#1 2023-11-21 23:30:31

Numerous Issues w/ Wayland

#2 2023-11-22 00:08:22

Re: Numerous Issues w/ Wayland

#3 2023-11-22 00:45:51

Re: Numerous Issues w/ Wayland

#4 2023-11-22 01:26:51

Re: Numerous Issues w/ Wayland

#5 2023-11-22 12:43:24

Re: Numerous Issues w/ Wayland

Board footer