Hi,
After the kernel update to 5.3.11-300.fc31.x86_64 (i think the previous one as well), my ASUS ROG Laptop gets stuck after hibernation. I am able to login and afterwards only the mouse is responsive. Any ideas?
Here is a some log output from journalctl -u gdm
-- Reboot --
Nov 15 10:14:23 autonomouscollar systemd[1]: Stopped GNOME Display Manager.
Nov 15 10:14:23 autonomouscollar systemd[1]: gdm.service: Succeeded.
Nov 15 10:14:23 autonomouscollar gdm[1099]: Freeing conversation 'gdm-launch-environment' with active job
Nov 15 10:14:23 autonomouscollar gdm[1099]: Tried to look up non-existent conversation gdm-launch-environment
Nov 15 10:14:23 autonomouscollar gdm[1099]: Freeing conversation 'gdm-password' with active job
Nov 15 10:14:23 autonomouscollar gdm[1099]: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
Nov 15 10:14:23 autonomouscollar systemd[1]: Stopping GNOME Display Manager...
Nov 15 09:38:05 autonomouscollar gdm-password][2427]: gkr-pam: unable to locate daemon control file
Nov 15 09:37:49 autonomouscollar gdm-password][2422]: gkr-pam: unable to locate daemon control file
Nov 15 09:37:49 autonomouscollar gdm-password][2422]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=mandos
Nov 15 09:37:41 autonomouscollar gdm-password][2417]: gkr-pam: unable to locate daemon control file
Nov 15 09:37:41 autonomouscollar gdm-password][2417]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=mandos
Nov 15 09:37:35 autonomouscollar gdm-password][2399]: gkr-pam: unable to locate daemon control file
Nov 15 09:37:31 autonomouscollar gdm-password][2399]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=mandos
Nov 15 03:47:15 autonomouscollar systemd[1]: Started GNOME Display Manager.
Nov 15 03:47:15 autonomouscollar systemd[1]: Starting GNOME Display Manager...
-- Reboot --
I think i misconfigured the pam configuration when I removed the Yubikey step, any ideas?
Here is the /etc/pam.d/gdm-password
auth [success=done ignore=ignore default=bad] pam_selinux_permit.so
auth substack password-auth
auth optional pam_gnome_keyring.so
auth include postlogin
account required pam_nologin.so
account include password-auth
password substack password-auth
-password optional pam_gnome_keyring.so use_authtok
session required pam_selinux.so close
session required pam_loginuid.so
session optional pam_console.so
session required pam_selinux.so open
session optional pam_keyinit.so force revoke
session required pam_namespace.so
session include password-auth
session optional pam_gnome_keyring.so auto_start
session include postlogin