Arch Linux

vixalien

Member

Registered: 2022-06-19

Posts: 10

[SOLVED] My GNOME session only runs x11, no wayland.

Hello. Whenever I try to login to my PC using GDM, it doesn't provide Wayland but instead lauches x11 sessions. On the cog wheel where you can select the desktop environment it just shows "GNOME" and "GNOME Classic" and when I click on "GNOME" it launches GNOME x11 instead of the usual wayland. Before, there used to be other options called "GNOME on Xorg" and "GNOME Classic on Xorg" but now they are gone. I have an Intel card (because apparently nvidia has issues with wayland).

Here's a link to my logs: http://0x0.st/HW9c.txt

Is there any way I can get back Wayland?

Last edited by vixalien (2023-10-04 22:31:10)

seth

Member

Registered: 2012-09-03

Posts: 60,051

Re: [SOLVED] My GNOME session only runs x11, no wayland.

Oct 04 19:38:33 dnezzar gnome-shell[1371]: Running GNOME Shell (using mutter 44.5) as a Wayland display server
…
Oct 04 19:38:34 dnezzar /usr/lib/gdm-wayland-session[1360]: dbus-daemon[1360]: [session uid=120 pid=1360] Activating service name='org.gnome.ScreenSaver' requested by ':1.24' (uid=120 pid=1618 comm="/usr/lib/gsd-power")
…
Oct 04 19:38:34 dnezzar kernel: gnome-shell[1371]: segfault at 0 ip 0000000000000000 sp 00007fff5cb797e8 error 14 likely on CPU 4 (core 0, socket 0)
Oct 04 19:38:34 dnezzar kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Oct 04 19:38:34 dnezzar systemd[1]: Created slice Slice /system/systemd-coredump.
Oct 04 19:38:34 dnezzar systemd[1]: Started Process Core Dump (PID 1787/UID 0).
…
Oct 04 19:38:35 dnezzar systemd-coredump[1788]: Process 1371 (gnome-shell) of user 120 dumped core.
                                                
                                                Stack trace of thread 1371:
                                                #0  0x0000000000000000 n/a (n/a + 0x0)
                                                ELF object binary architecture: AMD x86-64
Oct 04 19:38:35 dnezzar systemd[1]: systemd-coredump@0-1787-0.service: Deactivated successfully.

gnome/wayland dies w/ a stack corruption

Not sure whether that'S the cause, but it looks bad:

Oct 04 19:38:30 dnezzar systemd[1]: Starting Remount Root and Kernel File Systems...
Oct 04 19:38:30 dnezzar systemd-remount-fs[306]: mount: /: can't find UUID=6671a0f1-1541-4be2-8594-0d452bbd27dd.
Oct 04 19:38:30 dnezzar systemd-remount-fs[304]: /usr/bin/mount for / exited with exit status 1.
Oct 04 19:38:30 dnezzar systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
Oct 04 19:38:30 dnezzar systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'.
Oct 04 19:38:30 dnezzar systemd[1]: Failed to start Remount Root and Kernel File Systems.

"root=UUID=c686ea71-e969-4d74-a524-b2ed1d04c736" so fix your fstab?

If that's not it, add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters to get rid of the simpledrm device.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

bulletmark

Member

From: Brisbane, Australia

Registered: 2013-10-22

Posts: 680

Re: [SOLVED] My GNOME session only runs x11, no wayland.

The gnome-shell core dump is likely due to the bad mesa update 1:23.1.8-1 -> 1:23.2.1-1 from a few days ago. Downgrade to the previous mesa package and the problem goes away. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889.

vixalien

Member

Registered: 2022-06-19

Posts: 10

Re: [SOLVED] My GNOME session only runs x11, no wayland.

Thanks. I fixed my fstab and added the kernel parameter to no avail.

It's possible that it's an issue with the mesa package. I'll try downgrading and report back. Thanks

ceg

Member

Registered: 2022-08-14

Posts: 3

Re: [SOLVED] My GNOME session only runs x11, no wayland.

I can also confirm GNOME's GDM is only allowing me to pick x11 sessions and there is no Wayland option.

vixalien

Member

Registered: 2022-06-19

Posts: 10

Re: [SOLVED] My GNOME session only runs x11, no wayland.

@bulletmark your solution worked. the mesa update caused the issue. thanks.