You are not logged in.
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
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/1000This 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
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
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
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
apparently this is logged as a bug:
Failure is success in progress.
A.E.
Offline
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
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
In my case it was XDG_BIN_HOME set in .profile. Probably gnome is looking for something in that dir if variable is set and directory exist
IDK what's wrong now and I was so happy. to narrow down the issue I've created a new user directory and copy my settings from old one til I didn't get this "unable to localte..." on login, so it was .local/bin and XDG_BIN. By don't setting xdg var I was able to login into gnome, logout, change my tty and login into dwm environment. But after reboot gnome does not work again, pitty :/
UPD:
I accidentally shadowed some system executable with mine by writing a bad script to populate PATH var. Eh, entire day and useless post...
Last edited by Elbtalkessel (2020-09-29 17:58:34)
Offline