gkr-pam: unable to locate daemon control file

[Linuxfreak2]

Hi,
i have some issues with lightdm and lightlocker. I do not understand which does whom affect.
Unlocking the desktop with light-locker is buggy. And sometimes lightdm has back traces.

How can i track this down?

see:
the-cavalry/light-locker#139

see

journalctl -p 3 | grep light
Apr 23 20:58:02 lightdm[1629]: gkr-pam: unable to locate daemon control file
Apr 23 21:42:30 lightdm[14577]: gkr-pam: unable to locate daemon control file
Apr 24 12:18:05 lightdm[16857]: gkr-pam: unable to locate daemon control file
Apr 24 12:18:44 lightdm[17024]: gkr-pam: unable to locate daemon control file
Apr 24 12:59:08 lightdm[1726]: gkr-pam: unable to locate daemon control file
Apr 24 13:00:54 systemd-coredump[2004]: Process 1924 (light-locker) of ... 1000 dumped core.
#4 0x000055c8d5e98cb4 n/a (light-locker)
#9 0x000055c8d5e9b4f3 gs_listener_new (light-locker)
#10 0x000055c8d5e97484 n/a (light-locker)
#15 0x000055c8d5e97b03 gs_monitor_new (light-locker)
#16 0x000055c8d5e96339 main (light-locker)
#18 0x000055c8d5e9648e _start (light-locker)
Apr 24 13:14:33 lightdm[1366]: gkr-pam: unable to locate daemon control file
Apr 24 22:36:29 lightdm[1428]: gkr-pam: unable to locate daemon control file
Apr 24 22:36:38 lightdm[1500]: gkr-pam: unable to locate daemon control file
Apr 24 22:38:11 systemd-coredump[1713]: Process 1632 (light-locker) of ... 1000 dumped core.
#4 0x0000562c8001acb4 n/a (light-locker)
#9 0x0000562c8001d4f3 gs_listener_new (light-locker)
#10 0x0000562c80019484 n/a (light-locker)
#15 0x0000562c80019b03 gs_monitor_new (light-locker)
#16 0x0000562c80018339 main (light-locker)
#18 0x0000562c8001848e _start (light-locker)
Apr 26 12:24:28 lightdm[1041]: gkr-pam: unable to locate daemon control file
Apr 26 12:46:57 lightdm[1541]: gkr-pam: unable to locate daemon control file
Apr 26 13:30:13 lightdm[1936]: gkr-pam: unable to locate daemon control file
Apr 27 11:52:15 lightdm[5396]: gkr-pam: unable to locate daemon control file
Apr 27 12:40:44 lightdm[5938]: gkr-pam: unable to locate daemon control file
Apr 27 13:22:02 lightdm[6350]: gkr-pam: unable to locate daemon control file
Apr 27 14:38:29 lightdm[1029]: gkr-pam: unable to locate daemon control file
Apr 27 14:51:35 lightdm[1147]: gkr-pam: unable to locate daemon control file
Apr 27 14:51:43 lightdm[1159]: gkr-pam: unable to locate daemon control file

[Linuxfreak2]

see also:
https://forum.manjaro.org/t/lightdm-gkr-pam-unable-to-locate-daemon-control-file/85219

[Linuxfreak2]

right after unlocking the screen-locker:

Apr 29 18:17:07 lightdm[9653]: gkr-pam: unable to locate daemon control file
Apr 29 18:17:11 systemd-coredump[9659]: Process 690 (xfwm4) of user 1000 dumped core.

                                            Stack trace of thread 690:
                                            #0  0x00007fd8ed314186 n/a (libglib-2.0.so.0)
                                            #1  0x00007fd8ed311f5c g_log_writer_default (libglib-2.0.so.0)
                                            #2  0x00007fd8ed308a49 g_log_structured_array (libglib-2.0.so.0)
                                            #3  0x00007fd8ed310f0d g_log_structured_standard (libglib-2.0.so.0)
                                            #4  0x00007fd8ed66d54e n/a (libgdk-3.so.0)
                                            #5  0x00007fd8ed67a6e5 n/a (libgdk-3.so.0)
                                            #6  0x00007fd8ecf9552a _XError (libX11.so.6)
                                            #7  0x00007fd8ecf923f8 n/a (libX11.so.6)
                                            #8  0x00007fd8ecf924a5 n/a (libX11.so.6)
                                            #9  0x00007fd8ecf93410 _XReply (libX11.so.6)
                                            #10 0x00007fd8ede36742 XIQueryDevice (libXi.so.6)
                                            #11 0x00007fd8ed66a1bd n/a (libgdk-3.so.0)
                                            #12 0x00007fd8ed67536d n/a (libgdk-3.so.0)
                                            #13 0x00007fd8ed674e36 n/a (libgdk-3.so.0)
                                            #14 0x00007fd8ed63dea2 gdk_display_get_event (libgdk-3.so.0)
                                            #15 0x00007fd8ed674aa4 n/a (libgdk-3.so.0)
                                            #16 0x00007fd8ed31a7bf g_main_context_dispatch (libglib-2.0.so.0)
                                            #17 0x00007fd8ed31c739 n/a (libglib-2.0.so.0)
                                            #18 0x00007fd8ed31d6d2 g_main_loop_run (libglib-2.0.so.0)
                                            #19 0x00007fd8ed945e6f gtk_main (libgtk-3.so.0)
                                            #20 0x00005591c54a3765 n/a (xfwm4)
                                            #21 0x00007fd8eca44ce3 __libc_start_main (libc.so.6)
                                            #22 0x00005591c54a395e n/a (xfwm4)
                                            
                                            Stack trace of thread 699:
                                            #0  0x00007fd8ecb110d1 __poll (libc.so.6)
                                            #1  0x00007fd8ed31c690 n/a (libglib-2.0.so.0)
                                            #2  0x00007fd8ed31c77e g_main_context_iteration (libglib-2.0.so.0)
                                            #3  0x00007fd8ed31c7d2 n/a (libglib-2.0.so.0)
                                            #4  0x00007fd8ed2f7c21 n/a (libglib-2.0.so.0)
                                            #5  0x00007fd8ecbeda92 start_thread (libpthread.so.0)
                                            #6  0x00007fd8ecb1bcd3 __clone (libc.so.6)
                                            
                                            Stack trace of thread 700:
                                            #0  0x00007fd8ecb110d1 __poll (libc.so.6)
                                            #1  0x00007fd8ed31c690 n/a (libglib-2.0.so.0)
                                            #2  0x00007fd8ed31d6d2 g_main_loop_run (libglib-2.0.so.0)
                                            #3  0x00007fd8ec428568 n/a (libgio-2.0.so.0)
                                            #4  0x00007fd8ed2f7c21 n/a (libglib-2.0.so.0)
                                            #5  0x00007fd8ecbeda92 start_thread (libpthread.so.0)
                                            #6  0x00007fd8ecb1bcd3 __clone (libc.so.6)
                                            
                                            Stack trace of thread 841:
                                            #0  0x00007fd8ecbf3bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                            #1  0x00007fd8e88471e4 n/a (nouveau_dri.so)
                                            #2  0x00007fd8e8846f08 n/a (nouveau_dri.so)
                                            #3  0x00007fd8ecbeda92 start_thread (libpthread.so.0)
                                            #4  0x00007fd8ecb1bcd3 __clone (libc.so.6)

-- Subject: Speicherabbild für Prozess 690 (@COREDUMP_COMM) generiert
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)

-- Prozess 690 (xfwm4) ist abgebrochen worden und
-- ein Speicherabbild wurde generiert.

-- Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.

[Linuxfreak2]

XFCE people believing: it is entirely in gtk+ and the result
of an XError, I am not sure how that would relate to xfwm4.

[Linuxfreak2]

so how does lightdm cooperate/work/interact with gtk?

[khurshid-alam]

This is not a lightdm bug, gnome session binary giving this error. It seems your dconf is corrupted ( try mv ~/.config/dconf/user ~/.config/dconf/user.bak). See this issue.

[Linuxfreak2]

I am not on gnome, i use XFCE.

inxi -Fxzc0
System:
Host: Kernel: 5.1.1-2-MANJARO x86_64 bits: 64 compiler: gcc
v: 8.3.0 Desktop: Xfce 4.13.3git-b37930 Distro: Manjaro Linux

[Linuxfreak2]

right after unlocking the screen-locker:

Apr 29 18:17:07 lightdm[9653]: gkr-pam: unable to locate daemon control file
Apr 29 18:17:11 systemd-coredump[9659]: Process 690 (xfwm4) of user 1000 dumped core.

                                            Stack trace of thread 690:
                                            #0  0x00007fd8ed314186 n/a (libglib-2.0.so.0)
                                            #1  0x00007fd8ed311f5c g_log_writer_default (libglib-2.0.so.0)
                                            #2  0x00007fd8ed308a49 g_log_structured_array (libglib-2.0.so.0)
                                            #3  0x00007fd8ed310f0d g_log_structured_standard (libglib-2.0.so.0)
                                            #4  0x00007fd8ed66d54e n/a (libgdk-3.so.0)
                                            #5  0x00007fd8ed67a6e5 n/a (libgdk-3.so.0)
                                            #6  0x00007fd8ecf9552a _XError (libX11.so.6)
                                            #7  0x00007fd8ecf923f8 n/a (libX11.so.6)
                                            #8  0x00007fd8ecf924a5 n/a (libX11.so.6)
                                            #9  0x00007fd8ecf93410 _XReply (libX11.so.6)
                                            #10 0x00007fd8ede36742 XIQueryDevice (libXi.so.6)
                                            #11 0x00007fd8ed66a1bd n/a (libgdk-3.so.0)
                                            #12 0x00007fd8ed67536d n/a (libgdk-3.so.0)
                                            #13 0x00007fd8ed674e36 n/a (libgdk-3.so.0)
                                            #14 0x00007fd8ed63dea2 gdk_display_get_event (libgdk-3.so.0)
                                            #15 0x00007fd8ed674aa4 n/a (libgdk-3.so.0)
                                            #16 0x00007fd8ed31a7bf g_main_context_dispatch (libglib-2.0.so.0)
                                            #17 0x00007fd8ed31c739 n/a (libglib-2.0.so.0)
                                            #18 0x00007fd8ed31d6d2 g_main_loop_run (libglib-2.0.so.0)
                                            #19 0x00007fd8ed945e6f gtk_main (libgtk-3.so.0)
                                            #20 0x00005591c54a3765 n/a (xfwm4)
                                            #21 0x00007fd8eca44ce3 __libc_start_main (libc.so.6)
                                            #22 0x00005591c54a395e n/a (xfwm4)
                                            
                                            Stack trace of thread 699:
                                            #0  0x00007fd8ecb110d1 __poll (libc.so.6)
                                            #1  0x00007fd8ed31c690 n/a (libglib-2.0.so.0)
                                            #2  0x00007fd8ed31c77e g_main_context_iteration (libglib-2.0.so.0)
                                            #3  0x00007fd8ed31c7d2 n/a (libglib-2.0.so.0)
                                            #4  0x00007fd8ed2f7c21 n/a (libglib-2.0.so.0)
                                            #5  0x00007fd8ecbeda92 start_thread (libpthread.so.0)
                                            #6  0x00007fd8ecb1bcd3 __clone (libc.so.6)
                                            
                                            Stack trace of thread 700:
                                            #0  0x00007fd8ecb110d1 __poll (libc.so.6)
                                            #1  0x00007fd8ed31c690 n/a (libglib-2.0.so.0)
                                            #2  0x00007fd8ed31d6d2 g_main_loop_run (libglib-2.0.so.0)
                                            #3  0x00007fd8ec428568 n/a (libgio-2.0.so.0)
                                            #4  0x00007fd8ed2f7c21 n/a (libglib-2.0.so.0)
                                            #5  0x00007fd8ecbeda92 start_thread (libpthread.so.0)
                                            #6  0x00007fd8ecb1bcd3 __clone (libc.so.6)
                                            
                                            Stack trace of thread 841:
                                            #0  0x00007fd8ecbf3bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                            #1  0x00007fd8e88471e4 n/a (nouveau_dri.so)
                                            #2  0x00007fd8e8846f08 n/a (nouveau_dri.so)
                                            #3  0x00007fd8ecbeda92 start_thread (libpthread.so.0)
                                            #4  0x00007fd8ecb1bcd3 __clone (libc.so.6)

-- Subject: Speicherabbild für Prozess 690 (@COREDUMP_COMM) generiert

-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)

-- Prozess 690 (xfwm4) ist abgebrochen worden und

-- ein Speicherabbild wurde generiert.

-- Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.

Yup, this issue
systemd-coredump[9659]: Process 690 (xfwm4) of user 1000 dumped core.
i solved with the XFCE guys.

[Linuxfreak2]

I now use:
lightdm --version
lightdm 1.28.0
the issu: lightdm[9653]: gkr-pam: unable to locate daemon control file
is gone now.

But instead i have now:
journalctl -p 4 -b -0
lightdm[607]: gkr-pam: no password is available for user

[Linuxfreak2]

So? we can close gkr-pam: unable to locate daemon control file #70
and open
lightdm[607]: gkr-pam: no password is available for user
?

LF

Linux SS 4.19.42-1-MANJARO #1 SMP PREEMPT Fri May 10 20:52:43 UTC 2019 x86_64 GNU/Linux

still get this error,And my system is up to date

[sgse]

Jun 13 17:42:11 mx lightdm[1013]: gkr-pam: unable to locate daemon control file
[~] >> lightdm --version lightdm 1.28.0

[~] >> inxi -Fxzc0 System: Host: manjaro-xfce Kernel: 5.1.9-2-MANJARO x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: i3 4.16.1 Distro: Manjaro Linux

System is up to date.

[HaleTom]

Jul 12 17:15:52 svelte systemd-logind[644]: Lid opened.
Jul 12 17:15:55 svelte lightdm[21257]: gkr-pam: unable to locate daemon control file
Jul 12 17:15:55 svelte NetworkManager[13594]: <info>  [1562926555.7414] device (wlp2s0): supplicant interface state: disconnected -> scanning
Jul 12 17:15:55 svelte NetworkManager[13594]: <info>  [1562926555.7415] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Jul 12 17:15:56 svelte systemd[1]: session-c8.scope: Killing process 21201 (lightdm) with signal SIGTERM.
Jul 12 17:15:56 svelte systemd[1]: session-c8.scope: Killing process 21221 (lightdm-gtk-gre) with signal SIGTERM.
Jul 12 17:15:56 svelte systemd[1]: Stopping Session c8 of user lightdm.

Up to date Manjaro linux.

[das-nervt]

same here since weeks...
Jul 29 00:33:25 X3450 lightdm[918]: gkr-pam: unable to locate daemon control file
System: Host: X3450 Kernel: 5.2.2-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.1.0 Desktop: N/A Distro: Manjaro Linux
Kernel 4.16, 4.19, 5.2 all the same result,
any suggestions?

[volker-raschek]

same issue here..

journald log

markus@markus-nb:~$ journalctl --unit lightdm.service -f 
-- Logs begin at Mon 2019-03-25 17:19:21 CET. --
Aug 30 09:53:51 markus-nb lightdm[14303]: gkr-pam: unable to locate daemon control file
Aug 30 09:53:51 markus-nb lightdm[14303]: pam_unix(lightdm:session): session opened for user markus by (uid=0)
Aug 30 09:53:51 markus-nb lightdm[14303]: gkr-pam: unlocked login keyring
Aug 30 09:53:51 markus-nb lightdm[14303]: pam_unix(lightdm:session): session closed for user markus
Aug 30 09:53:52 markus-nb lightdm[14427]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)

System Informations

markus@markus-nb:~$ uname -a
Linux markus-nb 5.2.10-arch1-1-ARCH #1 SMP PREEMPT Sun Aug 25 18:01:31 UTC 2019 x86_64 GNU/Linux

[fernandoracca]

gkr-pam: unable to locate daemon control file

is not an issue specific to lightdm it seems.

I'm trying to track this problem that i'm currently experiencing on latest version of Ubuntu, 19.10, and it's just gdm3

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616

Even after backup /removal of dconf as @khurshid-alam suggested or even reset, it still doesn't work