Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43809 - Upgrading glibc problem with pam_unix (need rebuild?)

Attached to Project: Arch Linux
Opened by Vladimir (snigga) - Friday, 13 February 2015, 14:44 GMT
Last edited by Dave Reisner (falconindy) - Friday, 13 February 2015, 16:16 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Archlinux-current

With glibc 2.21.2 while trying to log in via vsftpd:


Feb 13 17:32:52 [vsftpd] PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libpthread.so.0: symbol __getrlimit, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Feb 13 17:32:52 [vsftpd] PAM adding faulty module: /usr/lib/security/pam_unix.so


glibc 2.21.1 works fine.
This task depends upon

Closed by  Dave Reisner (falconindy)
Friday, 13 February 2015, 16:16 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Programs which might dlopen libc components need to be restarted after upgrading libc.
Comment by Allan McRae (Allan) - Friday, 13 February 2015, 15:19 GMT
Does a reboot fix this? I guess it is trying to use libc.so.6 and libpthread.so.0 from different releases.
Comment by Dave Reisner (falconindy) - Friday, 13 February 2015, 15:33 GMT
Or just restart vsftpd. The same thing happens to cron after glibc releases.
Comment by Vladimir (snigga) - Friday, 13 February 2015, 15:56 GMT
Yep, it works after rebook. Thanks.

Loading...