Summary: | pam_unix.so doesnt work after sys-libs/glibc-2.9 upgrade | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeremy Huddleston Sequoia <jeremyhu> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED NEEDINFO | ||
Severity: | critical | CC: | axiator, wilscarlet |
Priority: | Highest | ||
Version: | 2008.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 270243 |
Description
Jeremy Huddleston Sequoia
2009-06-30 20:12:00 UTC
rebuilding pam fixed the problem for me... but still, this is something that needs to be addressed... your output doesnt show an ABI issue at all. it shows your libraries are out of sync. GLIBC_PRIVATE is something that only glibc libraries themselves should be using, and the version of libnsl.so.1 loaded needs to always match libc.so.6. if pam is using GLIBC_PRIVATE symbols, then it is broken. if you've re-emerged things and no one can reproduce, then there isnt anything to be done here. $ readelf -s /lib/libc.so.6 | grep libc_clnt 1962: 000fa120 936 FUNC GLOBAL DEFAULT 11 __libc_clntudp_bufcreate@@GLIBC_PRIVATE $ readelf -s /lib/libnsl.so.1 | grep libc_clnt 85: 00000000 936 FUNC GLOBAL DEFAULT UND __libc_clntudp_bufcreate@GLIBC_PRIVATE (11) $ readelf -s /lib/security/pam_unix.so | grep PRIVATE <nothing> I had this same issue. I had to reboot for the system to work properly again. i dont think you'd need to reboot, just restart the affected services xdm was the affected service. I restarted hal and xdm twice before reboot. If I had found this bug, I probably would have just rebuilt pam and continued on until the next problem cropped up. Also, since this upgrade, I have noticed other strange happenings like firefox crashing at random (usually with video), and I've already tried to rebuild the necessary programs for it including firefox. So, currently, I'm in the process of rebuilding everything (note: Don't know if it has been necessary for this step before, but usually I would automatically rebuild everything when gcc or glibc are upgraded anyway. But this time I decided to see what would happen.). Hopefully this will cure my issues once and for all. This Redhat bug report might help to understand the problem: https://bugzilla.redhat.com/show_bug.cgi?id=458825#c2 |