lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory

[dino99]

auth.log complaints:

Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so
Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm.
Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so
Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "oem"
Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for user oem by (uid=0)

As per lp:1309535 #18 comment such 'warnings' should be silenced (as they scared unawared users about the both needs of pam's gnome/kde)

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lightdm 1.13.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0
Uname: Linux 3.18.0-7-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.15.1-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Fri Dec 19 10:47:07 2014
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

[dino99 (9d9)]

Problem is still met on vivid i386, from journalctl (destop booted with systemd-sysv):

lightdm[970]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
lightdm[1033]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
lightdm[1033]: PAM adding faulty module: pam_kwallet.so
lightdm[1033]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)

[dino99 (9d9)]

Well these 'red lines' into journalctl are still logged. As its a design problem (lightdm is use on gnome & kde system, but with the same settings; indeed gnome complaint about the missing installed kde files, and vice versa)

It should be usefull to silence these harmless but annoying & scaring messages. Systemd might have such possibility.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Gannet (ken20001)]

Still on 18.04 (Xubuntu Linux i386).

[Daniel Richard G. (skunk)]

This issue persists in lightdm 1.30.0-0ubuntu3.1 in Ubuntu focal.

I see the warnings not only for pam_kwallet.so, but also its successor pam_kwallet5.so, as well as pam_gnome_keyring.so (which I do not have installed). All three of these are referenced in /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter as "optional" modules.

I attempted to eliminate the warnings by replacing the "optional" keyword with "[success=ok module_unknown=ignore default=ignore]", but that had no visible effect.

The entries referring to these modules need to be removed from LightDM's PAM config files. If libpam-gnome-keyring is installed, it will already make itself known to PAM via a pam-auth-update profile, which is the correct approach. The libpam-kwallet5 package has no pam-auth-update profile, but that is an issue for that package, not this one.

[RNZ (renoizer)]

I have same issue

[RNZ (renoizer)]

Also if apt purge lightdm and remove /var/lib/lightdm, after install this directory not created and lightmd can't start.

[Craig Harding (craigwharding)]

Seeing this in 20.04.1 with lightdm 1.30.0. see output attached.

[navycat (navycatt)]

This bug is present in Ubuntu 21.04 and 20.10 daily builds.

[navycat (navycatt)]

Ubuntu 21.10 bug present.

[Paul White (paulw2u)]

Removing EOL release tags

[Daniel Richard G. (skunk)]

This appears to have been addressed in bug #1949970 by making use of a feature of the PAM config. In /etc/pam.d/lightdm, I see e.g.

    -auth optional pam_gnome_keyring.so
    -auth optional pam_kwallet.so
    -auth optional pam_kwallet5.so

From the pam.conf(5) man page:

       If the *type* value from the list above
       is prepended with a - character the PAM
       library will not log to the system log if
       it is not possible to load the module
       because it is missing in the system. This
       can be useful especially for modules
       which are not always installed on the
       system and are not required for correct
       authentication and authorization of the
       login session.

I'll mark this issue as a duplicate of the newer one, even though it should be the other way around.