XDM service dead after Tumbleweed 4.6.2-1 update

Hey folks,

I recently upgraded my Dell Latitude E7440 laptop to the latest Tumbleweed release (4.6.2-1-Default) and the Gnome desktop is no longer working. Trying to perform some basic troubleshooting I ran SYSTEMCTL STATUS XDM.SERVICE and received the following response:

● display-manager.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2016-06-15 13:03:12 EDT; 3min 45s ago
Process: 9612 ExecStop=/usr/lib/X11/display-manager stop (code=exited, status=0/SUCCESS)
Process: 9624 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 9646 (gdm)
Tasks: 3 (limit: 512)
CGroup: /system.slice/display-manager.service
└─9646 /usr/sbin/gdm

Jun 15 13:03:35 Valaski-Afidenc gdm[9646]: Child process 14441 was already dead.
Jun 15 13:03:35 Valaski-Afidenc gdm[9646]: Unable to kill session worker process
Jun 15 13:03:35 Valaski-Afidenc gdm-launch-environment][14451]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Jun 15 13:03:35 Valaski-Afidenc /usr/lib/gdm/gdm-wayland-session[14454]: Unable to register display with display manager
Jun 15 13:03:35 Valaski-Afidenc gdm-launch-environment][14451]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Jun 15 13:03:35 Valaski-Afidenc gdm[9646]: Could not start command ‘/usr/lib/gdm/gdm-session-worker’: Too many open files
Jun 15 13:03:35 Valaski-Afidenc gdm[9646]: GLib: g_child_watch_add_full: assertion ‘pid > 0’ failed
Jun 15 13:03:35 Valaski-Afidenc gdm[9646]: Child process -14454 was already dead.
Jun 15 13:03:35 Valaski-Afidenc gdm[9646]: Child process 14451 was already dead.
Jun 15 13:03:35 Valaski-Afidenc gdm[9646]: Unable to kill session worker process

Any thoughts as to how to get this fixed?

Thanks!
Bill

Try to run this and reboot:

sudo pam-config --add --systemd

See here for more information:
http://lists.opensuse.org/opensuse-factory/2016-06/msg00113.html

That did the trick! thanks much for the pointer to the other post, I would never have found it looking for any of the messages from xdm.service.

Bill