Bug 1385151 - GDM authentication fails after reboot after kernel update
Summary: GDM authentication fails after reboot after kernel update
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 25
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-14 20:08 UTC by RobbieTheK
Modified: 2017-12-12 10:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:57:20 UTC
Type: Bug


Attachments (Terms of Use)

Description RobbieTheK 2016-10-14 20:08:16 UTC
Description of problem: 
Logins from local and NIS users fail.

Version-Release number of selected component (if applicable):
Name        : gdm
Arch        : x86_64
Epoch       : 1
Version     : 3.20.1
Release     : 3.fc24
Size        : 2.0 M
Repo        : @System

How reproducible:
almost always

Steps to Reproduce:
1. after kernel update, reboot

systemctl status gdm
* gdm.service - GNOME Display Manager
   Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2016-10-14 15:36:11 EDT; 5min ago
 Main PID: 9370 (gdm)
    Tasks: 3 (limit: 512)
   CGroup: /system.slice/gdm.service
           `-9370 /usr/sbin/gdm

gdm[9370]: Child process 22545 was already dead.
gdm[9370]: Unable to kill session worker process
gdm[9370]: Child process -22578 was already dead.
gdm[9370]: Child process 22569 was already dead.
gdm[9370]: Unable to kill session worker process
gdm[9370]: GdmDisplay: display lasted 0.139077 seconds
gdm[9370]: Could not start command '/usr/libexec/gdm-session-worker': Too many open files
gdm[9370]: GLib: g_child_watch_add_full: assertion 'pid > 0' failed
gdm[9370]: Child process 22590 was already dead.
gdm[9370]: Unable to kill session worker process


Here are some logs from /var/log/messages:

Oct 14 15:38:00 org.gnome.Shell.desktop: (gnome-shell:2049): GLib-GIO-CRITICAL **: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 14 15:38:00 org.gnome.Shell.desktop: (gnome-shell:2049): GLib-GIO-CRITICAL **: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Oct 14 15:38:00 org.gnome.Shell.desktop: (gnome-shell:2049): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct 14 15:38:49 org.gnome.Shell.desktop: (gnome-shell:2049): Gjs-WARNING **: JS ERROR: Gio.IOErrorEnum: The connection is closed
Oct 14 15:38:49 org.gnome.Shell.desktop: ShellUserVerifier<.cancel@resource:///org/gnome/shell/gdm/util.js:189
Oct 14 15:38:49 org.gnome.Shell.desktop: wrapper@resource:///org/gnome/gjs/modules/lang.js:178
Oct 14 15:38:49 org.gnome.Shell.desktop: AuthPrompt<.reset@resource:///org/gnome/shell/gdm/authPrompt.js:451
Oct 14 15:38:49 org.gnome.Shell.desktop: wrapper@resource:///org/gnome/gjs/modules/lang.js:178
Oct 14 15:38:49 org.gnome.Shell.desktop: AuthPrompt<.cancel@resource:///org/gnome/shell/gdm/authPrompt.js:522
Oct 14 15:38:49 org.gnome.Shell.desktop: wrapper@resource:///org/gnome/gjs/modules/lang.js:178
Oct 14 15:38:49 org.gnome.Shell.desktop: AuthPrompt<._init/<@resource:///org/gnome/shell/gdm/authPrompt.js:82
Oct 14 15:38:50 org.gnome.Shell.desktop: (gnome-shell:2049): Gjs-WARNING **: JS ERROR: Gio.IOErrorEnum: The connection is closed
Oct 14 15:39:01 systemd: Started Getty on tty3.
Oct 14 15:39:01 audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 14 15:39:02 org.gnome.Shell.desktop: (EE)
Oct 14 15:39:02 org.gnome.Shell.desktop: Fatal server error:
Oct 14 15:39:02 org.gnome.Shell.desktop: (EE) wl_display@1: error 0: invalid object 14
Oct 14 15:39:02 org.gnome.Shell.desktop: (EE)
Oct 14 15:39:02 gnome-settings-daemon.desktop: (gnome-settings-daemon:2084): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024.
Oct 14 15:39:02 kernel: traps: gnome-shell[2049] trap int3 ip:7f454297a15b sp:7fff1261fbe0 error:0 in libglib-2.0.so.0.4800.2[7f454292a000+10d000]
Oct 14 15:39:02 audit: ANOM_ABEND auid=4294967295 uid=42 gid=42 ses=4294967295 pid=2049 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=5
Oct 14 15:39:02 org.gnome.Shell.desktop: (gnome-shell:2049): mutter-ERROR **: Connection to xwayland lost
Oct 14 15:39:02 org.a11y.atspi.Registry: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1024"
Oct 14 15:39:02 org.a11y.atspi.Registry:      after 21 requests (21 known processed) with 0 events remaining.
Oct 14 15:39:02 gnome-session: gnome-session-binary[2035]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Oct 14 15:39:02 gnome-session-binary[2035]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Oct 14 15:39:02 abrt-hook-ccpp: Process 2049 (gnome-shell) of user 42 killed by SIGTRAP - dumping core
Oct 14 15:39:02 gnome-settings-daemon.desktop: ** (gnome-settings-daemon:22699): WARNING **: Unable to initialize GTK+
Oct 14 15:39:02 gnome-session: gnome-session-binary[2035]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Oct 14 15:39:02 gnome-session-binary[2035]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Oct 14 15:39:03 abrt-server: Deleting problem directory ccpp-2016-10-14-15:39:02-2049 (dup of ccpp-2016-09-09-16:15:19-1347)
Oct 14 15:39:03 gnome-session: gnome-session-binary[2035]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
Oct 14 15:39:03 gnome-session-binary: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 14 15:39:03 gnome-session-binary[2035]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
Oct 14 15:39:03 abrt-server: No actions are found for event 'notify-dup'
Oct 14 15:39:03 audit: USER_END pid=2019 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty1 res=success'
Oct 14 15:39:03 audit: CRED_DISP pid=2019 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty1 res=success'
Oct 14 15:39:27 systemd: Started Getty on tty4.
Oct 14 15:39:27 audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty4 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

From /var/log/secure
pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rh
AccountsService: ActUserManager: user (null) has no username (uid: 0)
pam_unix(gdm-password:auth): conversation failed
pam_unix(gdm-password:auth): auth could not identify password for
gkr-pam: error looking up user information
GdmDisplay: display lasted 0.026748 seconds

lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)



Oct 14 15:37:02 gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Oct 14 15:37:02 gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Oct 14 15:39:03 polkitd[5493]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.58, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Oct 14 15:39:03 gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Oct 14 15:44:05 polkitd[5493]: Registered Authentication Agent for unix-process:22899:1795788 (system bus name :1.2422 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Oct 14 15:44:05 polkitd[5493]: Unregistered Authentication Agent for unix-process:22899:1795788 (system bus name :1.2422, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Oct 14 15:44:12 polkitd[5493]: Registered Authentication Agent for unix-process:22911:1796512 (system bus name :1.2423 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Oct 14 15:44:12 polkitd[5493]: Unregistered Authentication Agent for unix-process:22911:1796512 (system bus name :1.2423, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Oct 14 15:44:13 gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Oct 14 15:44:14 polkitd[5493]: Registered Authentication Agent for unix-session:c508 (system bus name :1.2429 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)




Oct 14 15:51:00 linux-user-107 gnome-session: gnome-session-binary[31973]: CRITICAL: gsm_manager_set_phase: assertion 'GSM_IS_MANAGER (manager)' failed
Oct 14 15:51:00 linux-user-107 gnome-session-binary[31973]: CRITICAL: gsm_manager_set_phase: assertion 'GSM_IS_MANAGER (manager)' failed
Oct 14 15:51:00 linux-user-107 audit: USER_END pid=31958 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty1 res=success'
Oct 14 15:51:00 linux-user-107 audit: CRED_DISP pid=31958 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty1 res=success'
Oct 14 15:51:00 linux-user-107 gdm: GdmDisplay: display lasted 0.112095 seconds
Oct 14 15:51:00 linux-user-107 gdm: Could not start command '/usr/libexec/gdm-session-worker': Too many open files
Oct 14 15:51:00 linux-user-107 gdm: GLib: g_child_watch_add_full: assertion 'pid > 0' failed
Oct 14 15:51:00 linux-user-107 gdm: Child process 31958 was already dead.
Oct 14 15:51:00 linux-user-107 gdm: Unable to kill session worker process
Oct 14 15:51:00 linux-user-107 systemd-logind: Removed session c507.



Additional info:
Usually stopping GDM and then starting eventually works via systemctl

Comment 1 Fedora End Of Life 2017-07-25 23:28:51 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 19:25:46 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Fedora End Of Life 2017-11-16 18:43:58 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-12-12 10:57:20 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.