Arch Linux

I too have this exact issue using the Nvidia proprietary drivers. Rolling back to 3.26.1 fixes this temporarily

I also had this issue and downgraded back to 3.26.1.

This happened to me too, but with Wayland. When trying to login, it kicked me back to the login screen (gdm).
Gnome-Xorg works fine. But, when I select Gnome-Xorg, on next reboot, Gnome is selected.
Downgrading back to 3.26.1 and everything is ok.

Happened to me as well, downgraded to 3.26.1 after loading lxdm to confirm it was gdm.

In my case with Wayland after upgrading from 3.26.1 to 3.26.2 gives me the following errors and the UI does not come up

-- Reboot --
Okt 31 06:51:56 six kernel: acer_wmi: Unsupported machine has AMW0_GUID1, unable to load
Okt 31 06:51:59 six gnome-session-binary[460]: Unrecoverable failure in required component org.gnome.Shell.desktop
Okt 31 06:51:59 six gdm[416]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Okt 31 06:51:59 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.Shell.desktop
Okt 31 06:52:00 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Wacom.desktop
Okt 31 06:52:00 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.SettingsDaemon.XSettings.desktop
Okt 31 06:52:00 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.SettingsDaemon.A11yKeyboard.desktop
Okt 31 06:52:00 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Clipboard.desktop
Okt 31 06:52:00 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Okt 31 06:52:00 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop
Okt 31 06:52:00 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.SettingsDaemon.MediaKeys.desktop
Okt 31 06:52:00 six gnome-session-binary[546]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.Shell.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Wacom.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.SettingsDaemon.XSettings.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.SettingsDaemon.A11yKeyboard.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Clipboard.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.SettingsDaemon.MediaKeys.desktop
Okt 31 06:52:00 six gnome-session-binary[641]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop
.
.
.

Attached you can find the output of journalctl -o verbose MESSAGE="Unrecoverable failure in required component org.gnome.Shell.desktop" --since "2017-10-31 06:00:00"

Same problem here.

Can confirm. I have the WaylandEnable=false option uncommented.

confirmed, same here

and here too... downgrading gdm and libgdm to 3.26.1 is a workaround

No need to comment - just Vote (and watch) if you are affected.

I would say nvidia proprietary driver update even further complicates this issue. Logs are attached.
On my system I have to downgrade 4 packages in order to restore X working.
gdm-3.26.1-1
libgdm-3.26.1-1
nvidia-387.12-2
nvidia-387.12-2
I am running nvidia optimus powered laptop Asus K53. Wayland is intentionally disabled on both GDM and Gnome shell because of accessibility issues with Gnome on Wayland (such as https://bugzilla.gnome.org/show_bug.cgi?id=709999).
Edit: nvidia-387.22-3 is working fine as others have pointed out. So the gdm related issue remains on my system.

On my machine it works with the following versions:

- local/gdm 3.26.1-1 (gnome)
- local/libgdm 3.26.2-1
- local/nvidia 387.22-3
- local/nvidia-settings 387.12-1
- local/nvidia-utils 387.22-1

If I upgrade gdm to 3.26.2-1 it will break.

Just to confirm: upgrading libgdm (3.26.1-1 -> 3.26.2-1) and gdm (3.26.1-1 -> 3.26.2-1) brakes my system. In this case, I'm not using the proprietary Nvidia driver, but the open source nouveau. Using the Xorg or Wayland backed of GDM ended in a frozen system. Downgrading gdm and libgdm did fixed the issue.

Edit: Only need to downgrade gdm (3.26.1-1 -> 3.26.2-1), and stick with libgdm 3.26.2-1, to fix the issue.

Same here. I have WaylandEnable=true uncommented and am using the proprietary nvidia driver. No GDM for me, downgrade solves this however.

Happened to me here as well after the upgrate to the new GDM version.

- X11 with nvidia-driver and Wayland disabled

Downgrade of gdm and libgdm solves the problem. Had to restart the system by crossing the fingers and do the magic SysReq.

Can we get the journal log of a failed login with Enable=true in the [debug] section of /etc/gdm/custom.conf ?

Same here. Had to downgrade to GDM 3.26.1-1. Using proprietary NVIDIA drivers.

@heftig: Sure, here you go.

edit: Sorry, misread your request for debug enabled log. Please disregard this comment. :/

Resent nvidia (to 387.22-1) and gdm (to 3.26.2-1) package update broke down gnome shell desktop. System freezes when systemd starts gdm service. We were able to reproduce this bug on machine with same hardware. Journalcrl shows a lot of error messages with "Unrecoverable failure in required component org.gnome...". Downgrading nvidia to 387.12-2, nvidia-utils to 387.12-1 and gdm to 3.26.1-1 repairs gnome shell. I have also tried downgrade gdm package with new nvidia drivers and downgrade nvidia with new gdm but it didn't help.

@gegenschall It appears gdm debug was not enabled when you tried to repro...
Here is mine however I've only included gdm messages.
I guess gdm is trying to force wayland session here, I have no wayland session configured thus it exits with an error. Should I provide full log instead?

@arssivka nvidia-387.22-3 fixes the nvidia related brokennes however gdm failure still remains to be an issue.

Also, please test this build and report back:

https://pkgbuild.com/~heftig/gdm/

Install both packages.

The same error log here but with AMD drivers

extra/gdm 3.26.2-1 (gnome)
extra/libgdm 3.26.2-1
mesa-git/xf86-video-amdgpu-git 352.f6b39bc-1 (xorg-drivers)

Workaround Downgrading to
extra/gdm 3.26.1-1 (gnome)

Update the 2 pakages from https://pkgbuild.com/~heftig/gdm/ is working for me
extra/gdm 3.26.2-1.1 (gnome)
extra/libgdm 3.26.2-1.1

3.26.2-1.1 packages are also working fine for me.

Thanks. Unfortunately, the truncated gdm-service-only logs aren't enough; the interesting things happen in the session processes.

I have the same problem. Only the GNOME Xorg session works. GNOME Wayland does not work anymore.
I have:
$ lspci -k | grep -i -A 2 -E "(display|vga|3d)"
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
Subsystem: Gigabyte Technology Co., Ltd Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
Kernel driver in use: amdgpu
With Mesa, not AMDGPU-PRO.

https://bugzilla.gnome.org/show_bug.cgi?id=789722

I have made a new run to gather information in the debug mode.

Should be fixed in 3.26.2.1-1

3.26.2.1-1 works for me! thanks

3.26.2.1-1 works for me! thanks

Just wanted to say thanks for the fix! :)