Comment # 18 on bug 997486 from 
(Could finally log in.)
Indeed, the users dictd and syslogd-resolve had the same UID less than 500 in
my case. I removed the dictd package and the dictd user and rebooted then. Here
is what dmesg said afterwards:

...
[   10.675283] device-mapper: uevent: version 1.0.3
[   10.695348] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised:
dm-devel@redhat.com
[   11.427568] audit_printk_skb: 234 callbacks suppressed
[   11.427569] audit: type=1130 audit(1474584708.464:89): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=purge-kernels comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   11.427578] audit: type=1131 audit(1474584708.464:90): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=purge-kernels comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.868669] audit: type=1130 audit(1474584732.904:91): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=wicked comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.895091] audit: type=1130 audit(1474584732.928:92): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=rpc-statd-notify comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.895103] audit: type=1131 audit(1474584732.928:93): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=rpc-statd-notify comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.896999] audit: type=1130 audit(1474584732.932:94): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=iscsi comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.902211] audit: type=1130 audit(1474584732.936:95): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.919344] FS-Cache: Loaded
[   35.924573] FS-Cache: Netfs 'nfs' registered for caching
[   35.930078] audit: type=1130 audit(1474584732.502:96): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=ntpd comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   36.012741] Key type dns_resolver registered
[   36.017335] NFS: Registering the id_resolver key type
[   36.017342] Key type id_resolver registered
[   36.017343] Key type id_legacy registered
[   36.117162] audit: type=1130 audit(1474584732.690:97): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   36.119906] audit: type=1130 audit(1474584732.694:98): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   36.120281] audit: type=1130 audit(1474584732.694:99): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=after-local comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   36.125811] audit: type=1130 audit(1474584732.698:100): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=postfix comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   40.883626] audit_printk_skb: 250 callbacks suppressed
[   40.883629] audit: type=1101 audit(1474584737.458:183): pid=2268 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=? acct="?"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[   40.884590] audit: type=1130 audit(1474584737.458:184): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=user@465 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   40.884600] audit: type=1131 audit(1474584737.458:185): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=user@465 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   40.884859] audit: type=1105 audit(1474584737.458:186): pid=2264 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:session_open
grantors=pam_limits,pam_unix,pam_krb5,pam_umask,pam_ssh,pam_systemd,pam_gnome_keyring,pam_env
acct="gdm" exe="/usr/lib/gdm/gdm-session-worker" hostname=? addr=?
terminal=/dev/tty7 res=success'
[   41.019105] audit: type=1106 audit(1474584737.590:187): pid=2264 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=? acct="gdm"
exe="/usr/lib/gdm/gdm-session-worker" hostname=? addr=? terminal=/dev/tty7
res=failed'
[   41.019117] audit: type=1104 audit(1474584737.590:188): pid=2264 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit
acct="gdm" exe="/usr/lib/gdm/gdm-session-worker" hostname=? addr=?
terminal=/dev/tty7 res=success'
[   41.034591] audit: type=1100 audit(1474584737.606:189): pid=2278 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_permit
acct="gdm" exe="/usr/lib/gdm/gdm-session-worker" hostname=? addr=?
terminal=/dev/tty1 res=success'
[   41.034789] audit: type=1101 audit(1474584737.606:190): pid=2278 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit
acct="gdm" exe="/usr/lib/gdm/gdm-session-worker" hostname=? addr=?
terminal=/dev/tty1 res=success'
[   41.035066] audit: type=1103 audit(1474584737.606:191): pid=2278 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit
acct="gdm" exe="/usr/lib/gdm/gdm-session-worker" hostname=? addr=?
terminal=/dev/tty1 res=success'
[   41.070834] audit: type=1101 audit(1474584737.642:192): pid=2282 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=? acct="?"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[   46.389111] do_trap: 271 callbacks suppressed
[   46.389124] traps: gnome-shell[2526] trap int3 ip:7fbab35e574b
sp:7fff430e7b00 error:0
[   46.389137] audit: type=1701 audit(1474584742.962:282): auid=4294967295
uid=465 gid=462 ses=4294967295 pid=2526 comm="gnome-shell"
exe="/usr/bin/gnome-shell" sig=5
...

I'm now working remotely and cannot 100% confirm that gdm did not finally
start. However, trap int3 tell us that gnome-shell has most probably crashed.

You are receiving this mail because: