Elogind boot errors with Current
by upnort from LinuxQuestions.org on (#5BKNJ)
After updating my Current VM yesterday I see the following error messages:
Code:udevd[211]: failed to execute '/lib64/elogind/elogind-uaccess-command' '/lib64/elogind/elogind-uaccess-command /dev/sr0 ': No such file or directory
sshd[1792]: gkr-pam: unable to locate daemon control fileI don't see anything obvious in the change log.
In /etc/ssh/sshd_config, UsePAM=yes. A little searching indicates 'gkr-pam' has something to do with GNOME keyring?
The sshd seems to be a red herring. When I disable rc.sshd I see the error on login.
The errors appear booting to runlevel 3. X is not involved. When rc.S executes /dev/sr0 exists. Nominal digging indicates the elogind error is generated from the initrd.
Code:udevd[211]: failed to execute '/lib64/elogind/elogind-uaccess-command' '/lib64/elogind/elogind-uaccess-command /dev/sr0 ': No such file or directory
sshd[1792]: gkr-pam: unable to locate daemon control fileI don't see anything obvious in the change log.
In /etc/ssh/sshd_config, UsePAM=yes. A little searching indicates 'gkr-pam' has something to do with GNOME keyring?
The sshd seems to be a red herring. When I disable rc.sshd I see the error on login.
The errors appear booting to runlevel 3. X is not involved. When rc.S executes /dev/sr0 exists. Nominal digging indicates the elogind error is generated from the initrd.