You are not logged in.

#1 2020-04-06 00:26:18

URemery
Member
Registered: 2019-09-30
Posts: 14

[SOLVED] Gdm-password error : gkr-pam daemon control file not found

Hi everyone !

I noticed that gdm-password is reporting an error recently, here it is :

● gdm.service - GNOME Display Manager
     Loaded: loaded (/usr/lib/systemd/system/gdm.service; disabled; vendor preset: disabled)
     Active: active (running) since Mon 2020-04-06 01:09:16 CEST; 55min ago
   Main PID: 541 (gdm)
      Tasks: 3 (limit: 9397)
     Memory: 7.9M
     CGroup: /system.slice/gdm.service
             └─541 /usr/bin/gdm

avril 06 01:09:16 archlinux systemd[1]: Starting GNOME Display Manager...
avril 06 01:09:16 archlinux systemd[1]: Started GNOME Display Manager.
avril 06 01:09:51 archlinux gdm-password][832]: gkr-pam: unable to locate daemon control file
avril 06 01:09:51 archlinux gdm-password][832]: gkr-pam: stashed password to try later in open session
avril 06 01:09:52 archlinux gdm-password][832]: pam_unix(gdm-password:session): session opened for user ugor by (uid=0)
avril 06 01:09:52 archlinux gdm-password][832]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring

I've been looking for information about this mysterious file on the internet but couldn't find any.
It seems that it happened to other people sometimes, last report is a few months old but it's said that thses bugs where fixed in the meantime.

I've tried to start arch without loading gdm, authentifying then start gdm by hand just to see if gdm is started "too early". The error still appears in the journal after successfull login.

I've updated my system and gdm-3.34.1-2 is installed.

Do you have that same issue ? In case it may be linked to a recent update. Anyway, do you know how to fix this ?

Thank you, Ugo.

Last edited by URemery (2020-04-06 14:11:31)

Offline

#2 2020-04-06 06:24:53

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,743

Re: [SOLVED] Gdm-password error : gkr-pam daemon control file not found

Normal and well known and harmless.  Which is why the additional last message was added to tell you if everything was fine regardless of the "errors".

https://bugs.archlinux.org/task/62140
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28
https://gitlab.gnome.org/GNOME/gnome-ke … 46744d472e

Offline

#3 2020-04-06 14:11:13

URemery
Member
Registered: 2019-09-30
Posts: 14

Re: [SOLVED] Gdm-password error : gkr-pam daemon control file not found

As you said It has been "fixed" upstream and thus this error is harmless.
It might be a good idea to spend some time searching for a better solution than saying "ok it worked anyway".

Topic "SOLVED" but I'll may post a reply if I found something satisfying.

Thank you V1del

Offline

#4 2020-04-06 14:18:27

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,743

Re: [SOLVED] Gdm-password error : gkr-pam daemon control file not found

There is no issue. Gdm-password checks whether a file is set via an environment variable that is under normal circumstances in a systemd context not available at the time it first does the check. It will note that, and retry later when the session is there and PAM/systemd has set up the environments for your user.

It's an informal "error" most likely only relevant for systems that do not use systemd/logind, are embedded and single-user and start to actively fail when the file that is being checked for here is not present.

Offline

#5 2020-04-06 14:58:36

URemery
Member
Registered: 2019-09-30
Posts: 14

Re: [SOLVED] Gdm-password error : gkr-pam daemon control file not found

I understood why this error appears and why it's harmless. It might be useful not to throw errors when there isn't though. I'm just saying that there may be a way to avoid this "error" rather than saying "ok it worked anyway", it can be much clearer like this don't you think ?

Offline

#6 2020-04-06 15:01:24

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,743

Re: [SOLVED] Gdm-password error : gkr-pam daemon control file not found

I'd assume it's a much bigger investment if you have to include code that actively ensures this preemptively just so that you do not see a single line of log  that one might misinterpret as an error.

Offline

Board footer

Powered by FluxBB