Gkr-pam: unable to locate daemon control file

Project Discussion
#1

After the latest upgrade, I’m having trouble logging in with GDM. What happens:

  1. GDM shows login prompt despite auto-login being configured.
  2. Enter correct password → ‘incorrect password’ → ‘error while authenticating’ → jumps back into the main menu.
  3. Enter the correct password, again → continues → black screen → GDM again.

I can start the session via TTY → startx.

Some relevant stuff I found:

https://bugzilla.redhat.com/show_bug.cgi?id=1796544

The bug started happening after rebooting into 31.20200315.0, however booting back into 31.20200311.2 does not work.

Everything works correctly for new accounts. Removing ~/.local/share/gnome-shell (as per suggestion in the Arch bug) did not help.

#2

Found the culprit. A few days ago I put this into my .bashrc:

# Use fish as default shell
if [[ $(ps --no-header --pid=$PPID --format=cmd) != "fish" ]]
then
    exec fish
fi

Removing it fixes the problem. I’ll create a bug in gnome-keyring bug created.

#3

Also using fish, never edited my .bashrc, yet geting the error you mentioned.

1. # .bashrc

 * # Source global definitions

2. if [ -f /etc/bashrc ]; then

3. . /etc/bashrc

4. fi

 * # User specific environment

5. if ! [[ "$PATH" =~ "$HOME/.local/bin:$HOME/bin:" ]]

6. then

7. PATH="$HOME/.local/bin:$HOME/bin:$PATH"

8. fi

9. export PATH

 * # Uncomment the following line if you don't like systemctl's auto-paging feature:

10. # export SYSTEMD_PAGER=

 * # User specific aliases and functions

11. export PATH="/home/hades/.pyenv/bin:$PATH"

12. eval "$(pyenv init -)"

13. eval "$(pyenv virtualenv-init -)"
#4

Thank you for sharing this finding here, it has helped me to resolve 1910424 – gdm-password][2004]: gkr-pam: unable to locate daemon control file + Internal error: Could not resolve keysym XF86FullScreen.

1 Like