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!
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!
FS#33230 - [fcron] glibc/PAM/libpthread error from glibc 2.17-1
Attached to Project:
Arch Linux
Opened by Daniel Lublin (quite) - Friday, 28 December 2012, 19:52 GMT
Last edited by Dave Reisner (falconindy) - Friday, 28 December 2012, 20:26 GMT
Opened by Daniel Lublin (quite) - Friday, 28 December 2012, 19:52 GMT
Last edited by Dave Reisner (falconindy) - Friday, 28 December 2012, 20:26 GMT
|
DetailsSince glibc 2.17-1 Dec 28 20:30:00 kelebek fcron[9103]: PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libpthread.so. Dec 28 20:30:00 kelebek fcron[9103]: PAM adding faulty module: /usr/lib/security/pam_unix.so |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 28 December 2012, 20:26 GMT
Reason for closing: Not a bug
Friday, 28 December 2012, 20:26 GMT
Reason for closing: Not a bug
Comment by Dave Reisner (falconindy) -
Friday, 28 December 2012, 20:06 GMT
Happens every time there's a glibc update. Restart fcron.
Comment by Daniel Lublin (quite) -
Friday, 28 December 2012, 20:17 GMT
Ok, I thougt I had done that.. sorry. Seems to work now after a proper restart.