No wayland for Gnome

I don’t see any option to choose wayland for Gnome.

I have

[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false

section in /etc/gdm/custom.conf.

journalctl shows

May 15 11:52:11 hogwart systemd[7600]: Reached target GNOME Session Manager is ready.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished successfully.
░░ 
░░ The job identifier is 151.
May 15 11:52:11 hogwart systemd[7600]: Starting GNOME Shell on Wayland...
░░ Subject: A start job for unit UNIT has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has begun execution.
░░ 
░░ The job identifier is 148.
May 15 11:52:11 hogwart systemd[7600]: Starting GNOME Shell on X11...
░░ Subject: A start job for unit UNIT has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has begun execution.
░░ 
░░ The job identifier is 145.
May 15 11:52:11 hogwart systemd[7600]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
░░ Subject: Unit skipped
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit UNIT was skipped due to an ExecCondition= command failure, and has
░░ entered the 'dead' state with result 'exec-condition'.
May 15 11:52:11 hogwart systemd[7600]: Condition check resulted in GNOME Shell on Wayland being skipped.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished successfully.

Not sure where to find the exec-condition.

1 Like

Are you by any chance using proprietary Nvidia driver?

If so, have a look at this post from Manjaro forum. Perhaps it could resolve your issue:

2 Likes

Very good link. Thanks a lot.

I did 2. to disable the udev rule, then 3. to enable kms-modifiers. I skipped 4. because I am using dracut instead of grub. Not sure if anything should better be done here.

  1. was ok already.

Rebooting and now wayland is active.

Looking what journalctl tells

https://forum.manjaro.org/t/howto-use-wayland-with-proprietary-nvidia-drivers/36130
...
May 15 13:22:38 hogwart gnome-shell[2071]: Using public X11 display :0, (using :1 for managed services)
May 15 13:22:38 hogwart gnome-shell[2071]: Using Wayland display name 'wayland-0'
May 15 13:22:38 hogwart gnome-shell[2071]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
...
May 15 13:22:39 hogwart systemd[1973]: Started GNOME Shell on Wayland.
...
May 15 13:22:41 hogwart gnome-shell[2071]: GNOME Shell started at Mon May 15 2023 13:22:39 GMT+0200 (Central European Summer Time)
May 15 13:22:41 hogwart gnome-shell[2071]: Registering session with GDM
May 15 13:22:41 hogwart gnome-shell[1440]: Connection to xwayland lost
May 15 13:22:41 hogwart gnome-shell[1440]: Xwayland terminated, exiting since it was mandatory
May 15 13:22:41 hogwart org.gnome.Shell.desktop[1440]: GNOME Shell terminated with an error: Xwayland exited unexpectedly
May 15 13:22:41 hogwart gnome-shell[1440]: (../mutter/src/core/meta-context.c:501):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop))
May 15 13:22:41 hogwart gnome-shell[1440]: Shutting down GNOME Shell

Not sure about the last messages as all is seemingly working ok.

Not sure what they are. Seems to be related to xwayland.

If you want to implement what was suggested in step 4 in the link above but adapt it to dracut+systemd-boot, you could have a look at the links below for how to add kernel modules in dracut and boot parameters in systemd-boot:

https://discovery.endeavouros.com/installation/dracut/2022/12/

https://discovery.endeavouros.com/installation/systemd-boot/2022/12/

Thanks, I will take a look.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.