Will try to come up with a minimal reproducer. Currently it takes
several hours to run the complete test, and a few hours before the SEGV
occurs. But the stack trace is always identical when it happens. In
multiple runs, it always succeeds on the host and always fails in the
VM.
--
You received t
I think we can close this out, we were able to reproduce the issue
without kvm. Sorry for the false alarm.
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
** Changed in: openldap (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openldap (Ubuntu)
Status: Invali
As I noted in our ITS#8025, this has nothing to do with upstream
OpenLDAP. It may be specific to the particular way you built OpenLDAP in
your distro, or it may be due to pam_ldap itself, but neither of these
are in the purview of the OpenLDAP Project. Certainly there is nothing
in vanilla OpenLDAP
Try replacing pam-ldap/nss-ldap with nslcd and/or nssov and see if the
problem persists. I'd bet it doesn't. See here
https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/comments/84
for reasons why you should have abandoned pam-ldap/nss-ldap years ago.
--
You received this bug notification
4 matches
Mail list logo
