Arch Linux

Caspian

Member

Registered: 2007-05-22

Posts: 263

[SOLVED] GDM failing to start with Wayland since update to 43

This morning complete Gnome stack was updated to 43 on my system. After the update GDM fails to start. I only get a black screen and can't even switch to one of the other terminals (I need to force shutdown with the power button and edit boot line to enter multi user target.
When I force the usage of X11 the GDM starts as expected.
I would like to avoid using X11, since everything works much smoother under Wayland for me.
I have a laptop with Nvidia Optimus, but I've disabled Nvidia card with udev rules (I've checked and lspci doesn't report that the Nvidia card exists).

Here's the output of 'journalctl -u gdm' for the last two failed startups:

-- Boot 36c4f019ceec47a3a7037c86ef1b7694 --
Nov 01 13:11:19 nebula systemd[1]: Starting GNOME Display Manager...
Nov 01 13:11:19 nebula systemd[1]: Started GNOME Display Manager.
Nov 01 13:11:26 nebula gdm[590]: Gdm: Tried to look up non-existent conversation gdm-launch-environment
Nov 01 13:11:26 nebula gdm[590]: Gdm: GdmDisplay: Session never registered, failing
Nov 01 13:11:26 nebula systemd[1]: Stopping GNOME Display Manager...
Nov 01 13:11:26 nebula gdm[590]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.10 was not provided by any .service files
Nov 01 13:11:26 nebula systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
Nov 01 13:11:26 nebula systemd[1]: gdm.service: Failed with result 'exit-code'.
Nov 01 13:11:26 nebula systemd[1]: Stopped GNOME Display Manager.
Nov 01 13:11:26 nebula systemd[1]: gdm.service: Triggering OnFailure= dependencies.
Nov 01 13:11:26 nebula systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.
-- Boot f05c029db8ad4cacaf93287dcc9c6c3a --
Nov 01 13:19:42 nebula systemd[1]: Starting GNOME Display Manager...
Nov 01 13:19:42 nebula systemd[1]: Started GNOME Display Manager.
Nov 01 13:20:17 nebula gdm[658]: Gdm: Tried to look up non-existent conversation gdm-launch-environment
Nov 01 13:20:17 nebula gdm[658]: Gdm: GdmDisplay: Session never registered, failing
Nov 01 13:20:17 nebula gdm[658]: Gdm: GdmDisplay: Session never registered, failing
Nov 01 13:20:17 nebula gdm[658]: Gdm: Freeing conversation 'gdm-launch-environment' with active job
Nov 01 13:20:17 nebula systemd[1]: Stopping GNOME Display Manager...
Nov 01 13:20:18 nebula systemd[1]: gdm.service: Deactivated successfully.
Nov 01 13:20:18 nebula systemd[1]: Stopped GNOME Display Manager.

Is anyone else experiencing similar issues or has any suggestions?

Last edited by Caspian (2022-11-04 08:26:37)

VoDo

Member

From: Europe

Registered: 2020-06-04

Posts: 122

Re: [SOLVED] GDM failing to start with Wayland since update to 43

same problem on my x280
someone wrote a bug report already https://bugs.archlinux.org/?project=1&string=gdm

---

Archi3

Caspian

Member

Registered: 2007-05-22

Posts: 263

Re: [SOLVED] GDM failing to start with Wayland since update to 43

Thanks for the info VoDo. At least I'm not the only one with the issue...

knoopx

Member

Registered: 2022-11-02

Posts: 1

Re: [SOLVED] GDM failing to start with Wayland since update to 43

same here, also happened previously when trying FCGU repository. I was using mutter-x11-scaling. disabling wayland is a workaround.

Cornul11

Member

Registered: 2022-02-02

Posts: 8

Re: [SOLVED] GDM failing to start with Wayland since update to 43

Removing gstreamer-vaapi as a workaround also fixed the issue for me.

matryoshka

Member

Registered: 2022-05-14

Posts: 17

Re: [SOLVED] GDM failing to start with Wayland since update to 43

Removing gstreamer-vaapi as a workaround also fixed the issue for me.

That also allowed me to start gnome. Thanks, but how did you know this was the current issue?

ps: lenovo ideapad 5 pro 14acn6

Last edited by matryoshka (2022-11-03 05:53:48)

Caspian

Member

Registered: 2007-05-22

Posts: 263

Re: [SOLVED] GDM failing to start with Wayland since update to 43

Same here; removing gstreamer-vaapi is a workaround to get wayland working.
@matryoshka: See here for more details: https://bugs.archlinux.org/task/76368?s … &closedto=

morarch

Member

Registered: 2015-10-06

Posts: 5

Re: [SOLVED] GDM failing to start with Wayland since update to 43

Another workaround that I found here is to comment this line in

/etc/pam.d/system-auth
#-account   [success=1 default=ignore]  pam_systemd_home.so

Afterwards I can launch the gnome-session on Wayland without removing gstreamer-vaapi.

Caspian

Member

Registered: 2007-05-22

Posts: 263

Re: [SOLVED] GDM failing to start with Wayland since update to 43

electrickite in the bug report posted above found a better solution to this issue (at least for users using Intell); installing intel-media-driver package. With this package installed there's no need for uninstalling gstreamer-vaapi.
I'm marking this as solved, since this solves the issue completely for me, without the need for removing pacakges.