Description of problem: Something happening today, presumably a DNF update I ran, just broke UI login, for me. I keep kicked "kicked back" to the account chooser. I happen to have had SSH, so I was able to run "journalctl -f" while it happened. Version-Release number of selected component (if applicable): Fedora 33 with DNF updates as of today. How reproducible: I'm not sure - I'll see if I can reproduce it on a fresh install on a VM. I'll also keep the physical machine where this happens around, if you want more logs. Steps to Reproduce: Attempt to login. Expected results: Never manage to login on UI, always falls back to Login Screen. Actual results: Dec 23 22:09:07 ixo gdm-password][2004]: gkr-pam: unable to locate daemon control file Dec 23 22:09:07 ixo audit[2004]: USER_AUTH pid=2004 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam_unix,pam_gnome_keyring acct="vorburger" exe="/usr/libexec/gdm-session-worker" hostname=ixo addr=? terminal=/dev/tty1 res=success' Dec 23 22:09:07 ixo gdm-password][2004]: gkr-pam: stashed password to try later in open session Dec 23 22:09:07 ixo audit[2004]: USER_ACCT pid=2004 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="vorburger" exe="/usr/libexec/gdm-session-worker" hostname=ixo addr=? terminal=/dev/tty1 res=success' Dec 23 22:09:07 ixo audit[2004]: CRED_ACQ pid=2004 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix,pam_gnome_keyring acct="vorburger" exe="/usr/libexec/gdm-session-worker" hostname=ixo addr=? terminal=/dev/tty1 res=success' Dec 23 22:09:07 ixo audit[2004]: USER_ROLE_CHANGE pid=2004 uid=0 auid=1000 ses=6 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 exe="/usr/libexec/gdm-session-worker" hostname=ixo addr=? terminal=/dev/tty2 res=success' Dec 23 22:09:07 ixo systemd-logind[823]: [🡕] New session 6 of user vorburger. Dec 23 22:09:07 ixo systemd[1]: Started Session 6 of user vorburger. Dec 23 22:09:07 ixo gdm-password][2004]: pam_unix(gdm-password:session): session opened for user vorburger(uid=1000) by (uid=0) Dec 23 22:09:07 ixo gdm-password][2004]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring Dec 23 22:09:07 ixo audit[2004]: USER_START pid=2004 uid=0 auid=1000 ses=6 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_gnome_keyring,pam_umask acct="vorburger" exe="/usr/libexec/gdm-session-worker" hostname=ixo addr=? terminal=/dev/tty2 res=success' Dec 23 22:09:07 ixo kernel: rfkill: input handler enabled Dec 23 22:09:07 ixo uresourced[1020]: Setting resources on user-42.slice (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100) Dec 23 22:09:07 ixo uresourced[1020]: Setting resources on user (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100) Dec 23 22:09:07 ixo uresourced[1020]: Setting resources on user-1000.slice (MemoryMin: 262144000, MemoryLow: 0, CPUWeight: 500, IOWeight: 500) Dec 23 22:09:07 ixo uresourced[1020]: Setting resources on user (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100) Dec 23 22:09:07 ixo gdm-password][2004]: pam_unix(gdm-password:session): session closed for user vorburger Dec 23 22:09:07 ixo audit[2004]: USER_END pid=2004 uid=0 auid=1000 ses=6 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_gnome_keyring,pam_umask acct="vorburger" exe="/usr/libexec/gdm-session-worker" hostname=ixo addr=? terminal=/dev/tty2 res=success' Dec 23 22:09:07 ixo audit[2004]: CRED_DISP pid=2004 uid=0 auid=1000 ses=6 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix,pam_gnome_keyring acct="vorburger" exe="/usr/libexec/gdm-session-worker" hostname=ixo addr=? terminal=/dev/tty2 res=success' Dec 23 22:09:07 ixo gdm[983]: Gdm: GdmDisplay: Session never registered, failing Dec 23 22:09:07 ixo kernel: rfkill: input handler disabled Dec 23 22:09:07 ixo systemd[1]: session-6.scope: Succeeded. Dec 23 22:09:07 ixo systemd-logind[823]: Session 6 logged out. Waiting for processes to exit. Dec 23 22:09:07 ixo systemd-logind[823]: [🡕] Removed session 6. Dec 23 22:09:08 ixo uresourced[1020]: Setting resources on user-1000.slice (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100) Dec 23 22:09:08 ixo uresourced[1020]: Setting resources on user (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100) Dec 23 22:09:08 ixo uresourced[1020]: Setting resources on user-42.slice (MemoryMin: 262144000, MemoryLow: 0, CPUWeight: 500, IOWeight: 500) Dec 23 22:09:08 ixo uresourced[1020]: Setting resources on user (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100) Dec 23 22:09:08 ixo org.gnome.Shell.desktop[2164]: The XKEYBOARD keymap compiler (xkbcomp) reports: Dec 23 22:09:08 ixo org.gnome.Shell.desktop[2164]: > Warning: Unsupported maximum keycode 569, clipping. Dec 23 22:09:08 ixo org.gnome.Shell.desktop[2164]: > X11 cannot support keycodes above 255. Dec 23 22:09:08 ixo org.gnome.Shell.desktop[2164]: > Internal error: Could not resolve keysym XF86FullScreen Dec 23 22:09:08 ixo org.gnome.Shell.desktop[2164]: Errors from xkbcomp are not fatal to the X server
I searched more online, and stumbled upon https://discussion.fedoraproject.org/t/gkr-pam-unable-to-locate-daemon-control-file/18102, which mentions an "exec fish" at the end of .bashrc.. just like I had in my https://github.com/vorburger/vorburger-dotfiles-bin-etc/blob/fac76f69bf0e706e103c02e762ede2c34cf1072a/dotfiles/bashrc#L40 You can reproduce this by installing Fedora Workstation 33 from scratch in Boxes (and I then ran an initial "sudo dnf update"; but that's actually probably not even required), then do "sudo dnf install fish" and "echo '[ -s /usr/bin/fish ] && [[ $(ps --no-header --pid=$PPID --format=cmd) != "fish" ]] && exec fish' >>.bashrc" and Logout and try to Log In again, and boum, you hit this problem. Perhaps "exec fish" in .bashrc is dumb (but "chsh -s /bin/fish" didn't work for me..), and I'll try to update https://wiki.archlinux.org/index.php/Fish#Modify_.bashrc_to_drop_into_fish which recommended that, but is it really normal that a GDM can be thrown off that badly by .bashrc? Why does a Display manager graphical login prompt even care about the shell? PS: https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/28 has something that looked related, but wasn't it (for me).
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.