You are not logged in.

#1 2020-06-12 11:19:56

ps_143
Member
Registered: 2016-07-15
Posts: 2

gdm-password gkr-pam: unable to locate daemon control file

When starting the system the the cursor just blinks and gdm doesn't start.
When simply switching to other tty session and coming back starts gdm.
Output for journalctl --unit gdm.service -f

-- Logs begin at Fri 2020-06-12 03:38:39 IST. --
Jun 12 16:18:33 AwesomePC gdm[459]: GLib: g_hash_table_foreach: assertion 'version == hash_table->version' failed
Jun 12 16:18:33 AwesomePC systemd[1]: gdm.service: Succeeded.
Jun 12 16:18:33 AwesomePC systemd[1]: Stopped GNOME Display Manager.
-- Reboot --
Jun 12 16:18:46 AwesomePC systemd[1]: Starting GNOME Display Manager...
Jun 12 16:18:46 AwesomePC systemd[1]: Started GNOME Display Manager.
Jun 12 16:18:47 AwesomePC gdm[482]: Child process -544 was already dead.
Jun 12 16:20:21 AwesomePC gdm-password][859]: gkr-pam: unable to locate daemon control file
Jun 12 16:20:21 AwesomePC gdm-password][859]: gkr-pam: stashed password to try later in open session
Jun 12 16:20:21 AwesomePC gdm-password][859]: pam_unix(gdm-password:session): session opened for user pr09eek by (uid=0)
Jun 12 16:20:21 AwesomePC gdm-password][859]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring

Offline

#2 2020-06-12 14:09:12

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 15,077

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

That message is harmless. Does pressing random buttons instead of explicitly switching tty, help as well?

If so try adding

random.trust_cpu=on

to your kernel parameters or if you happen to not trust the CPU give https://wiki.archlinux.org/index.php/Haveged a shot.

Offline

#3 2020-06-12 20:52:01

ps_143
Member
Registered: 2016-07-15
Posts: 2

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

V1del wrote:

That message is harmless. Does pressing random buttons instead of explicitly switching tty, help as well?

If so try adding

random.trust_cpu=on

to your kernel parameters or if you happen to not trust the CPU give https://wiki.archlinux.org/index.php/Haveged a shot.

Your solution did solve another issue of random seed but not this one. : (

Jun 12 23:15:38 AwesomePC gdm[529]: Child process -573 was already dead.
Jun 12 23:17:17 AwesomePC gdm-password][2102]: gkr-pam: unable to locate daemon control file
Jun 12 23:17:17 AwesomePC gdm-password][2102]: gkr-pam: stashed password to try later in open session
Jun 12 23:17:17 AwesomePC gdm-password][2102]: pam_unix(gdm-password:session): session opened for user pr09eek by (uid=0)
Jun 12 23:17:17 AwesomePC gdm-password][2102]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Jun 12 23:17:20 AwesomePC gdm[529]: Child process -1884 was already dead.
Jun 12 23:40:45 AwesomePC gdm[529]: GLib: Source ID 145 was not found when attempting to remove it
Jun 13 00:55:00 AwesomePC gdm[529]: GLib: Source ID 151 was not found when attempting to remove it
Jun 13 01:16:07 AwesomePC gdm[529]: GLib: Source ID 157 was not found when attempting to remove it
Jun 13 02:16:07 AwesomePC gdm[529]: GLib: Source ID 163 was not found when attempting to remove it

After switching to lts kernal starts gdm without any problem.

Offline

Board footer

Powered by FluxBB