Arch Linux

Same here, I downgraded gdm to 3.16 as a workaround. I attached my logs.

Same happened to me tiday , downgrading gdm only to 3.16.0 fixed it

The X output http://pastebin.com/dk55YT9p

I use a bumblebee setup (intel+nvidia)

Made my home laptop (which is set to login with gdm into gnome at boot) go into a loop at boot.

What looks like repeated restarts of gdm also hinders typing in a username and password at the console (ctrl-alt-Fx). For users with this setup, and a long and cryptic password, rebooting in single user mode would be the only solution, as they would not be able to type in the password without the input being interrupted.

The same thing here....

Downgrading GDM and LIBGDM to 3.16.0 save my day :)

This workaround does the trick:

pacman -U /var/cache/pacman/pkg/*gdm*-3.16.0.1-*

Same problem here, gdm dumps core.
Downgrading gdm only (not libgdm) to 3.16.0.1 solved the problem.

Only downgrading gdm did not work here. Intel graphics card, open source drivers. Downgrading both gdm and libgdm worked.

Here is the upstream bug tracker for gdm: https://bugzilla.gnome.org/page.cgi?id=browse.html&product=gdm

More information here:  FS#44588 

Just upgrade to 3.16.1-2 and everything is working fine!
https://www.archlinux.org/packages/extra/x86_64/gdm/

That was a fast fix, thanks

Confirmed working now

I think having to reboot in single user mode because gdm restarts in a way that does not allow users to type in their passwords at the console qualifies as "severe boot failure that is likely to affect more than just you" (ref https://wiki.archlinux.org/index.php/Reporting_bug_guidelines#Severity).

Before I upgraded to gdm 3.16.1-2, I tried to dig out the problem. It seems that gdm wants to try Walyand backend first, which is a new feature in GNOME 3.16:

https://mail.gnome.org/archives/gnome-announce-list/2015-March/msg00071.html
"The login screen is now using Wayland by default."

It will fallback to X backend if fails.

However, there are two problems:
1. Archlinux does not have xorg-server-xwayland as a/an (optional) dependency of gdm, and thus gdm complains about no Xwayland.
2. gdm does not fall back to X backend once wayland fails. Instead, it continues to try wayland for at least three times (which you can see from the log).
*. If you switch to other tty and switch back, gdm will finally start the X backend.

The two problems combined cause no login screen. I installed xorg-server-xwayland and that solved the problem, before 3.16.2 rolling out.

I've just upgraded to the current gdm versions before I typed this comment:

[2015-04-17 08:06] [ALPM] upgraded libgdm (3.16.1-3 -> 3.16.1.1-1)
[2015-04-17 08:06] [ALPM] upgraded gdm (3.16.1-3 -> 3.16.1.1-1)

Both this current and the previous version have a 100% repeatable (I think related) bug which occurs across all my platforms where Arch is installed. I use auto-login and if I log out then I never get an X login window. I also can not get virtual terminals. If I disable auto-login and reboot then GDM does present a login window. This occurs if I log in with GNOME or with GNOME with wayland.

I updated to the latest versions, tried every combination i could in /etc/gdm/custom.conf but only autologin let me enter the desktop: after that, i need to manually unlock the gnome password keyring if i want ie. Chromium to use it, or the gnome-keyring-daemon will hang indefinitely at 100% CPU usage.

i downgraded to gdm and libgdm 3.16.1-3 but nothing...

hope these help as well...

and here is the gdm log.

Try installing nm-connection-editor, this fixed problems with gdm and gnome-shell for me.

https://bbs.archlinux.org/viewtopic.php?pid=1527421#p1527421

This issue is really annoying. Downgrading (and upgrading to the newest gdm) did not help.

Whenever I boot my machine I see the login screen normally, but I get a "blank screen" after I login. I have to manually kill gnome-shell (at another tty) and then things start to work normally. When I uncomment "#WaylandEnable=false" in custom.cfg, then the machine is unusable (previous method does not work).

Part of the `journalctl -r -u gdm` is attached.

I have an intel graphic card (Lenovo t420s) + mesa, nm-connection-editor installed, intel microcode updates configured.

Please try loading your display driver early by adding its module (e.g. i915 or radeon or nouveau) to modules-load.d.

Unfortunately that did not help (I added i915 as shown here https://wiki.archlinux.org/index.php/Kernel_mode_setting#Installation and rebuilt the image with mkinitcpio). Still gdm dumps core and killing gnome-shell helps.
Not sure if relevant, but my configuration forces edid in KMS to allow using the needed external screen resolution (as shown here https://wiki.archlinux.org/index.php/Kernel_mode_setting#Forcing_modes_and_EDID).

Upstream report:
https://bugzilla.gnome.org/show_bug.cgi?id=751308

Also seen in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1232786

I think I managed to solve the issue (gnome starts normally after logging in), but I am not sure exactly how--I installed gdm3setup and made some changes to the configuration...

Has anybody found a solution/workaround? Or are people still suffering from this?

@nalimilan My personal workaround back then was to install wayland (along with xorg-server-xwayland). I looked into the logs and at least my crashes were caused by missing wayland (gdm 3.16 started to use wayland for the login screen by default). Wayland was added as a dependency of gdm in https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/gdm&id=e7c3e0b58cc9a94dd968aaf0baa3731a499226fb .

And I believe some people were running into other crashes, and it seems 3.16.1.1 fixed them. Not sure why there were still crash reports after 3.16.1.1 (e.g. @bulletmark), but I tend to think those are independent issues.

@Hexcles, as I said at the time, this bug started with 3.16.1-3 + 3.16.1.1-1 and was 100% reproducible. Anyhow, we have long since moved to 3.18+ and the bug does not occur anymore for me.

Thank you both. I'm actually a Fedora user, but I'm trying to gather more information for upstream. I'm still experiencing the bug with GDM 3.18, but I'll investigate enabling Wayland (which crashes GDM for me currently). That said, GDM should still work with X, as long as this option is provided.