Arch Linux

Description:

There seems to be a race condition some sort, where the systemd tries to start gnome-session before drm is properly intialized. As a consequence the login screen never comes up. I can work around the problem by switching to another console and running 'systemctl restart gdm'

Additional info:
* linux 4.2.5-1, gnome-session 3.18.1.2-1, gdm 3.18.0-1

From the logs it can be seen that there is an error not finding the drm device, which is true. It is only initialized afterwards.

--- clip ---
Nov 02 21:42:57 xxxxxxxxxx kernel: [drm] Initialized radeon 2.43.0 20080528 for 0000:01:00.0 on minor 0
--- clip ---
Nov 02 21:42:57 xxxxxxxxxx systemd-coredump[549]: Process 545 (gnome-shell) of user 120 dumped core.
Nov 02 21:42:57 xxxxxxxxxx gdm-launch-environment][555]: pam_systemd(gdm-launch-environment:session): Failed to create session: Resource deadlock avoided
Nov 02 21:42:57 xxxxxxxxxx systemd-logind[476]: Failed to start session scope session-c2.scope: Transaction is destructive. org.freedesktop.systemd1.Transact
--- clip ---
Nov 02 21:42:57 xxxxxxxxxx gnome-session-binary[536]: Unrecoverable failure in required component gnome-shell-wayland.desktop
Nov 02 21:42:57 xxxxxxxxxx gnome-session[536]: gnome-session-binary[536]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 5
Nov 02 21:42:57 xxxxxxxxxx gnome-session-binary[536]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 5
Nov 02 21:42:56 xxxxxxxxxx kernel: traps: gnome-shell[545] trap int3 ip:7f346b5c164b sp:7fff7ca6efe0 error:0
Nov 02 21:42:56 xxxxxxxxxx gnome-session[536]: (gnome-shell:545): mutter-ERROR **: could not find drm kms device
--- clip ---

Steps to reproduce:
- Just start up the machine, sometimes it happens, sometimes it doesn't