Comment 3 for bug 1768488

The following other bugs reports say the same thing: #1861598 and #1830079

I also find the same bug in Xubuntu 20.04 and in my own custom 20.04 Ubuntu. As the bug number here is the smallest, I'll assume it is the first one that has reported it.

I stumbled upon this bug while trying to find why some good computer would crash suddenly with Xubuntu 20.04. Another issue related to ACPI is probably what was happening, however looking out for other bugs while I am at it is something to be done. I also experience some crashes in my own computer at home where no ACPI issue is mentioned in the logs, but this “pam_kwallet*” related message is in my logs. (Not anymore next session because I commented out the lines in the /etc/pam.d/lightdm and lightdm-greeter files, but I know this might be a temporary turn-around if it is not fixed upstream, right?)

Now my first question is : what package does this bug belong to? Is is lightdm as it seems from this present bug report? I might say "yes", because wajig gives information about the packages pam_kwallet belong to, in particular, this part of the error message is interesting:

“ PAM adding faulty module: pam_kwallet.so ”

Well, there is no such file in the kwallet packages.

In details:

***
wajig whichpackage pam_kwallet
UNINSTALLED MATCHES (x3)
------------------------
libpam-kwallet5: /lib/x86_64-linux-gnu/security/pam_kwallet5.so
libpam-kwallet-common: /etc/xdg/autostart/pam_kwallet_init.desktop
libpam-kwallet-common: /usr/share/libpam-kwallet-common/pam_kwallet_init
***

what files do libpam-kwallet5 and libpam-kwallet-common bring in? The wajig command will also answer this question:
***
wajig listfiles libpam-kwallet5
libpam-kwallet5: /lib/x86_64-linux-gnu/security/pam_kwallet5.so
libpam-kwallet5: /usr/share/doc/libpam-kwallet5/changelog.Debian.gz
libpam-kwallet5: /usr/share/doc/libpam-kwallet5/copyright
***

So first thing first, the lines relating to "pam_kwallet.so" should just be removed from the files lightdm and lightdm-greeter, because it simply does not exist, so I guess this is why the message states it is a "faulty module".

As for the rest of the error message from the system, "PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory"
I have no idea what can be done, but surely we need to do something about it.
Does PAM provide other types of conditions when it comes to try to load modules?

Or might there be another way to tell it not to try loading it if we are not in a KDE environment?