I can confirm the problem, however I cannot confirm the solutions.
I still get this:
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) illegal module type: @include
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-auth]
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) no module name supplied
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM unable to dlopen(<*unknown module path*>)
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM [error: <*unknown module path*>: cannot open shared object file: No such file or directory]
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM adding faulty module: <*unknown module path*>
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) illegal module type: @include
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-account]
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) no module name supplied
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) illegal module type: @include
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-auth]
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) no module name supplied
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) illegal module type: @include
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-account]
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) no module name supplied
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) illegal module type: @include
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-password]
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) no module name supplied
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) illegal module type: @include
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-session]
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) no module name supplied
Eventually my problem is caused by the fact that I had VMWare's tarball installed previously and eventually their uninstall script might have left some traces iiritating Canonical's packaged version.
I switched back to the VMWare tarball and it's fine for me now.
This is one of the apps where I like to stay at the bleeding edge anyway (Bleeding edge means being ahead of any distribution most of the time and using upstream tarballs all the time).
I can confirm the problem, however I cannot confirm the solutions.
I still get this:
Dec 24 15:38:44 vz02 vmware- authd[19308] : PAM (vmware-authd) illegal module type: @include authd[19308] : PAM pam_parse: expecting return value; [...common-auth] authd[19308] : PAM (vmware-authd) no module name supplied authd[19308] : PAM unable to dlopen(<*unknown module path*>) authd[19308] : PAM [error: <*unknown module path*>: cannot open shared object file: No such file or directory] authd[19308] : PAM adding faulty module: <*unknown module path*> authd[19308] : PAM (vmware-authd) illegal module type: @include authd[19308] : PAM pam_parse: expecting return value; [...common-account] authd[19308] : PAM (vmware-authd) no module name supplied authd[19308] : PAM (other) illegal module type: @include authd[19308] : PAM pam_parse: expecting return value; [...common-auth] authd[19308] : PAM (other) no module name supplied authd[19308] : PAM (other) illegal module type: @include authd[19308] : PAM pam_parse: expecting return value; [...common-account] authd[19308] : PAM (other) no module name supplied authd[19308] : PAM (other) illegal module type: @include authd[19308] : PAM pam_parse: expecting return value; [...common- password] authd[19308] : PAM (other) no module name supplied authd[19308] : PAM (other) illegal module type: @include authd[19308] : PAM pam_parse: expecting return value; [...common-session] authd[19308] : PAM (other) no module name supplied
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Dec 24 15:38:44 vz02 vmware-
Eventually my problem is caused by the fact that I had VMWare's tarball installed previously and eventually their uninstall script might have left some traces iiritating Canonical's packaged version.
I switched back to the VMWare tarball and it's fine for me now.
This is one of the apps where I like to stay at the bleeding edge anyway (Bleeding edge means being ahead of any distribution most of the time and using upstream tarballs all the time).