This is really a pam bug.
vmware-server uses pam as shipped in ia32-libs. pam hardcodes the
/lib/security path, but on amd64 installations, this is where the 64-bit
pam modules are, so we end up with a 32 bit application tryin to dlopen
a 64 bit binary, which obviously doesn't work. What needs to be done in
pam is to check if (uname says we're running 64 bit && we're compiled
for 32 bit) we should go looking in /lib32/security instead.
** Changed in: pam (Ubuntu)
Sourcepackagename: None => pam
Assignee: VMware Build Team (vmware-builds) => (unassigned)
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
