I can confirm this error running.
I managed to get a little further by using the following pam configuration :
auth sufficient /usr/lib/vmware/lib/libpam.so.0/security/pam_unix.so shadow
null ok
auth required /usr/lib/vmware/lib/libpam.so.0/security/pam_unix_auth.so shadow
nullok
account sufficient /usr/lib/vmware/lib/libpam.so.0/security/pam_unix.so
account required /usr/lib/vmware/lib/libpam.so.0/security/pam_unix_acct.so
Now my authd.log produces :
May 26 04:31:00 desktop1 vmware-authd[8767]: PAM (other) illegal module type:
@include
May 26 04:31:00 desktop1 vmware-authd[8767]: PAM pam_parse: expecting return
value; [...common-auth]
May 26 04:31:00 desktop1 vmware-authd[8767]: PAM (other) no module name supplied
May 26 04:31:00 desktop1 vmware-authd[8767]: PAM unable to dlopen(<*unknown
module path*>)
May 26 04:31:00 desktop1 vmware-authd[8767]: PAM [error: <*unknown module
path*>: cannot open shared object file: No such file or directory]
May 26 04:31:00 desktop1 vmware-authd[8767]: PAM adding faulty module:
<*unknown module path*>
Note... I have also unsuccessfully tried using the following in my pam
configuration as suggested by another:-
@include common-auth
@include common-account
** Changed in: vmware-package (Ubuntu)
Status: New => Confirmed
--
amd64 + vmware 1.0.9 vmware-authd broken
https://bugs.launchpad.net/bugs/363272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
