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#22623 - [glibc] Upgrading 2.12.2-2 to 2.13-1 breaks PAM

Attached to Project: Arch Linux
Opened by Daniel Lublin (quite) - Thursday, 27 January 2011, 10:39 GMT
Last edited by Ionut Biru (wonder) - Thursday, 27 January 2011, 14:25 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details


[2011-01-27 09:52] upgraded glibc (2.12.2-2 -> 2.13-1)

Jan 27 10:01:00 kelebek fcron[23156]: PAM unable to dlopen(/lib/security/pam_unix.so): /lib/libnsl.so.1: symbol __libc_rpc_getport, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Jan 27 10:01:00 kelebek fcron[23156]: PAM adding faulty module: /lib/security/pam_unix.so
Jan 27 10:01:00 kelebek fcron[23156]: Could not init PAM account management for '/usr/sbin/run-cron /etc/cron.hourly': Module is unknown
Jan 27 10:01:00 kelebek fcron[23156]: Job '/usr/sbin/run-cron /etc/cron.hourly' has *not* run.

What gives? Is this something that could possibly be resolved by recompiling PAM and/or fcron?

Perhaps it should've been reported for PAM, but glibc did break my PAM...
This task depends upon

Closed by  Ionut Biru (wonder)
Thursday, 27 January 2011, 14:25 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Thursday, 27 January 2011, 10:50 GMT
You should restart fcron to get this working again. Fcron dlopens new glibc libraries trough pam (pam_unix.so links to libnsl.so.1). The new glibc libraries won't work with the old libc.so.6 that was already loaded when fcron was started.
Comment by Daniel Lublin (quite) - Thursday, 27 January 2011, 11:16 GMT
Ah, thanks for enlighting me. As a new Arch user, I now recall the glibc post-install script in Debian, reporting that some services need to be restarted and proceeding to do so.
Comment by Christian Hesse (eworm) - Thursday, 27 January 2011, 13:26 GMT
xscreensaver temporarily fails as well... I was locked from my machine. The workaround is to switch to the console, login and do
# kill `pidof xscreensaver`

Loading...