You are not logged in.

#1 2019-03-22 18:52:15

olocin
Member
Registered: 2018-01-03
Posts: 166

gkr-pam: unable to locate daemon control file

Recently, I've been getting at login errors of type

 login[580]: gkr-pam: unable to locate daemon control file 

in my journal.
Sometimes the error seems harmless and key-ring unlocks just fine, sometimes other errors follow

login[2467]: couldn't read data from gnome-keyring-daemon: Connection reset by peer
login[2453]: gkr-pam: couldn't unlock the login keyring.

and I have to unlock it by hand.

There are a few topics on this forum about it, and also some commits on the gnome key-ring git-lab that claim to have fixed it already 2 weeks ago.
I'm using dwm, and configured the key-ring according to the arch wiki, both editing pam and .xinitrc, and I login just using the tty console.
Is it possible that the bug is still there?

Offline

#2 2019-03-26 12:17:08

chrisdb
Member
From: Belgium
Registered: 2018-05-16
Posts: 124

Re: gkr-pam: unable to locate daemon control file

I'm getting something similar.

gkr-pam: unable to locate daemon control file 

Are you also running XFCE?

This error would indicate that the env variable 'XDG_RUNTIME_DIR' is not set.

But mine is:

/run/user/1000

This seems correct to me....

Although I'm getting this message, my keyring works because I can succesfully connect to my wireless which is only saved for my user.

Last edited by chrisdb (2019-03-26 12:19:01)


Failure is success in progress.
A.E.

Offline

#3 2019-03-26 12:40:10

loqs
Member
Registered: 2014-03-06
Posts: 8,833

Re: gkr-pam: unable to locate daemon control file

olocin wrote:

on the gnome key-ring git-lab that claim to have fixed it already 2 weeks ago.

Commit used by gnome-keyring 3.31.91 is 1c834760190ecf5a58c6feee441c41baeea07f5f [1] [2]
The only commits I can see after that are translation updates [3] [4].

[1] https://git.archlinux.org/svntogit/pack … 7af6c6#n16
[2] https://gitlab.gnome.org/GNOME/gnome-ke … baeea07f5f
[3] https://gitlab.gnome.org/GNOME/gnome-ke … 3df3d7cd1f
[4] https://gitlab.gnome.org/GNOME/gnome-ke … 07f96a74c0

Offline

#4 2019-03-26 13:02:50

olocin
Member
Registered: 2018-01-03
Posts: 166

Re: gkr-pam: unable to locate daemon control file

I'm using dwm.
Indeed I thought commit 2a20a7ac9667bdb68b2c9d553d1fee0f3425f6d4 and the one before it dealt precisely with this issue, but perhaps I'm wrong?

Offline

#5 2019-03-26 13:20:06

loqs
Member
Registered: 2014-03-06
Posts: 8,833

Re: gkr-pam: unable to locate daemon control file

https://gitlab.gnome.org/GNOME/gnome-ke … 9b67f1324a does not remove the error message
I think what the change does is when [1] [2] or [3] is reached the daemon will be started because need_daemon will now be set to 1.
I would suggest investigating the later messages unfortunately I can not offer any insight into the cause.

login[2467]: couldn't read data from gnome-keyring-daemon: Connection reset by peer
login[2453]: gkr-pam: couldn't unlock the login keyring.

[1] https://gitlab.gnome.org/GNOME/gnome-ke … ule.c#L886
[2] https://gitlab.gnome.org/GNOME/gnome-ke … ule.c#L941
[3] https://gitlab.gnome.org/GNOME/gnome-ke … le.c#L1027

Offline

#6 2019-03-26 19:45:31

chrisdb
Member
From: Belgium
Registered: 2018-05-16
Posts: 124

Re: gkr-pam: unable to locate daemon control file

apparently this is logged as a bug:

https://bugs.archlinux.org/task/62140


Failure is success in progress.
A.E.

Offline

#7 2019-03-26 21:44:26

loqs
Member
Registered: 2014-03-06
Posts: 8,833

Re: gkr-pam: unable to locate daemon control file

chrisdb wrote:

apparently this is logged as a bug

Registration on the bugtracker is open and after registering anything can then be filed as a bug.

Offline

#8 2019-03-27 08:57:52

chrisdb
Member
From: Belgium
Registered: 2018-05-16
Posts: 124

Re: gkr-pam: unable to locate daemon control file

loqs wrote:
chrisdb wrote:

apparently this is logged as a bug

Registration on the bugtracker is open and after registering anything can then be filed as a bug.

Sorry, I wasn' aware of this

The issue really seems like the env variable "XDG_RUNTIME_DIR" is set too late....
But the daemon is started anyway...


Failure is success in progress.
A.E.

Offline

Board footer

Powered by FluxBB