Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#62140 - [lightdm] gkr-pam: unable to locate daemon control file

Attached to Project: Arch Linux
Opened by Kristian (Nexrem) - Monday, 25 March 2019, 22:47 GMT
Last edited by David Runge (dvzrv) - Friday, 17 January 2020, 11:00 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Maxime Gauduin (Alucryd)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 30
Private No


Systemd journal reports
lightdm[455]: gkr-pam: unable to locate daemon control file

lightdm seems to work fine, allowing me to log in and continue operation.
This issue did not exist in 1:1.28.0-1

Additional info:
* package version(s): 1:1.28.0-3

Steps to reproduce:
1. Let lightdm launch
2. Check systemd journal
This task depends upon

Comment by Jan Przybylak (jp) - Tuesday, 09 April 2019, 17:06 GMT
I also get this error on KDE, so it's not caused by lightdm.
Comment by Kristian (Nexrem) - Wednesday, 10 April 2019, 16:28 GMT
Must be gnome-keyring then
Comment by Jan Przybylak (jp) - Wednesday, 10 April 2019, 17:56 GMT
Could also be PAM
Comment by Lorenzo Porta (Vindex17) - Friday, 26 April 2019, 09:52 GMT Comment by Lex Sheehan (l3x) - Thursday, 12 September 2019, 12:16 GMT
The last error recorded in my journal before my system locked up:

`Sep 12 07:41:37 k3 lightdm[849]: gkr-pam: unable to locate daemon control file`

Unable to bring up a virtual terminal: Ctrl + Alt + F1, (F1-F6). Mouse frozen, etc.

Happens at random times.

Same behavior for XFCE and GNOME.

Will downgrade lightdm and try for a while to see if the system locks stop.

Kernel: 5.2.13-arch1-1-ARCH x86_64 bits: 64 compiler: gcc v: 9.1.0 Desktop: Xfce 4.14.1 Distro: Arch Linux
lightdm version: 1.30.0
Comment by Lex Sheehan (l3x) - Saturday, 14 September 2019, 19:15 GMT
After downgrading from lightdm 1.30.0 to 1.28.0 I have discovered that downgrading did not help. My system is still locking up with the same `Sep 14 15:07:03 k3 lightdm[852]: gkr-pam: unable to locate daemon control file` message.

Any recommendations on how best to troubleshoot this issue?

Comment by Lucas Amador de Oliveira (amadorzcv) - Friday, 29 November 2019, 00:21 GMT
I also have this bug. System locks up randomly and i get the gkr-pam: unable to locate daemon control file on journal
Comment by Li (orzogc) - Tuesday, 10 March 2020, 15:35 GMT Comment by John Bug (johnbug) - Thursday, 14 May 2020, 17:54 GMT
Bug still present.
Comment by Tun Win Naing (twnaing) - Tuesday, 15 September 2020, 02:45 GMT
I have the bug with gnome-keyring 3.36, lightdm 1.30 with Kernel 5.8.6
Comment by John Piers (johnpiers) - Saturday, 10 October 2020, 18:48 GMT
Sender lightdm
Time 19:27:25
Message gkr-pam: unable to locate daemon control file
Priority 3

I see the last person who commented was on the 2020-09-15 so don't know if this is still an issue but I presume that it is. My system is also locking up randomly with lightdm gkr-pam: unable to locate daemon control file` message

I'm using gnome-shell 1:3.38.1-1, gnome-keyring 1:3.36.0-1, lightdm 1:1.30.0-4, linux 5.8.14.arch1-1

Comment by Bart (sleeping) - Monday, 04 January 2021, 17:36 GMT
Same issue with gdm

Bugged when I boot with enabled service
Works if I start service after boot
Comment by Siegfried Metz (NiceGuy) - Tuesday, 16 February 2021, 19:37 GMT
Planned for Fedora 34 in 2021:
'The monolithic daemon provided by GNOME Keyring will be split into dedicated sub-daemons, so that they can be consistently managed by systemd.'

Should help in general to fix this annoying error, if it can be implemented in time or there is enough developer effort.