Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 4519

Summary: pam-0.68-1 /lib/security/pam_unix.so undefined sym yperr_string
Product: [Retired] Red Hat Raw Hide Reporter: dunwoody
Component: pamAssignee: Cristian Gafton <gafton>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-08-27 23:15:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description dunwoody 1999-08-14 09:20:13 UTC
In pam-0.68-1, /lib/security/pam_unix.so references
the symbol yperr_string, which leads to messages like
the following in /var/log/messages:

Aug 14 01:24:34 dunwoody1 su: PAM unable to
dlopen(/lib/security/pam_unix_acct.so)
Aug 14 01:24:34 dunwoody1 su: PAM [dlerror:
/lib/security/pam_unix_acct.so: undefined symbol:
yperr_string]
Aug 14 01:24:34 dunwoody1 su: PAM adding faulty module:
/lib/security/pam_unix_acct.so

I'm wondering if perhaps there is a new dependency from pam
to some other package that I don't happen to have installed,
and the pam-0.68-1 rpm doesn't enforce that dependency?

Comment 1 Cristian Gafton 1999-08-27 23:15:59 UTC
Fixed in pam-0.68-3 and later