Kernel issues since -22

[Dale Amon]

That does sound a lot like the existing issues and is
disturbing news. But I've lived with it for 4 years
so I guess I can deal with it longer.

However, the new issues seem different. There are things
like coming up to the mate login panel and being unable to
log in because something is not set up. A reboot usually fixes it:

Jun 20 12:21:25 otv3 lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such 
file or directory
Jun 20 12:21:25 otv3 lightdm: PAM adding faulty module: pam_kwallet.so
Jun 20 12:21:25 otv3 lightdm: PAM unable to dlopen(pam_kwallet5.so): 
/lib/security/pam_kwallet5.so: cannot open shared object file: No such 
file or directory
Jun 20 12:21:25 otv3 lightdm: PAM adding faulty module: pam_kwallet5.so
Jun 20 12:21:25 otv3 lightdm: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "amon"
Jun 20 12:21:33 otv3 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm

On the working -21 I see this during boots; I am wondering if this is 
the place where -22,23 and 24 fail:

[   20.990720] systemd[1]: friendly-recovery.service: Found ordering 
cycle on friendly-recovery.service/start
[   20.990725] systemd[1]: friendly-recovery.service: Found dependency 
on root.mount/start
[   20.990728] systemd[1]: friendly-recovery.service: Found dependency 
on local-fs-pre.target/start
[   20.990729] systemd[1]: friendly-recovery.service: Found dependency 
on friendly-recovery.service/start
[   20.990731] systemd[1]: friendly-recovery.service: Breaking ordering 
cycle by deleting job root.mount/start
[   20.990733] systemd[1]: root.mount: Job root.mount/start deleted to 
break ordering cycle starting with friendly-recovery.service/start
[   20.991194] systemd[1]: Reached target Encrypted Volumes.