Bug 2298941 - gkr-pam: unable to locate daemon control file
Summary: gkr-pam: unable to locate daemon control file
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-20 05:37 UTC by Steve
Modified: 2026-01-05 05:11 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-20 19:15:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-keyring issues 28 0 None closed Gkr-pam: unable to locate daemon control file 2026-01-05 05:11:48 UTC

Description Steve 2024-07-20 05:37:22 UTC
Copying from this bug against "gdm":

Bug 2250521 - gdm-session-wor: gkr-pam: unable to locate daemon control file 

Error is reported in system logs.

Reproducible: Always

Steps to Reproduce:
1. Login to GNOME session

Actual Results:  
Error is reported in system logs

Expected Results:  
It would be nice if there were no error messages in logs related to default system components.


Reproducible: Always





The message occurs with lightdm too:

$ journalctl --no-hostname -b -g gkr
Jul 19 13:57:10 lightdm[1398]: gkr-pam: unable to locate daemon control file
Jul 19 13:57:10 lightdm[1398]: gkr-pam: stashed password to try later in open session
Jul 19 13:57:11 lightdm[1398]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring

The "daemon control file" appears to be a socket:

$ sudo lsof -w -l +c0 +D /run/user/1000/keyring/
COMMAND         PID     USER   FD   TYPE             DEVICE SIZE/OFF  NODE NAME
gnome-keyring-d 974     1000    6u  unix 0x00000000bec26e08      0t0 10977 /run/user/1000/keyring/control type=STREAM (LISTEN)

$ rpm -q gnome-keyring lightdm
gnome-keyring-46.2-1.fc40.x86_64
lightdm-1.32.0-10.fc40.x86_64

Comment 1 Aoife Moloney 2025-04-28 13:31:50 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Aoife Moloney 2025-05-20 19:15:20 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Christian Stadelmann 2026-01-05 05:11:48 UTC
Still present in Fedora 43 (both on atomic and non-atomic GNOME version at least). See also: https://discussion.fedoraproject.org/t/important-log-errors-in-new-install-of-silverblue/178975

More info in the upstream bug report: https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/28


Note You need to log in before you can comment on or make changes to this bug.