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#53233 - libc.so.6: version `GLIBC_2.25' not found
Attached to Project:
Arch Linux
Opened by Anna (kalterfx) - Friday, 10 March 2017, 03:15 GMT
Last edited by Allan McRae (Allan) - Friday, 10 March 2017, 05:53 GMT
Opened by Anna (kalterfx) - Friday, 10 March 2017, 03:15 GMT
Last edited by Allan McRae (Allan) - Friday, 10 March 2017, 05:53 GMT
|
DetailsDescription:
Since March 8 glibc was released in testing repository, this software contains a bug. Recently I tried to run X server, but it failed due to the following error: Mar 10 07:29:32 kfxlaptop systemd[11625]: PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib/libcrypt.so.1) Mar 10 07:29:32 kfxlaptop systemd[11625]: PAM adding faulty module: /usr/lib/security/pam_unix.so libcrypt.so is also part of glibc. Additional info: * package version(s): glibc-2.25-1 * config and/or log files etc: http://ix.io/oQT Steps to reproduce: Enable testing repo in pacman.conf and install glibc. |
This task depends upon
Comment by Allan McRae (Allan) -
Friday, 10 March 2017, 03:51 GMT
Sounds like you have software using libc.so.6 and libcrypt.so.1 from different glibc versions. Restarting that software or a system reboot will fix that.
Comment by Anna (kalterfx) -
Friday, 10 March 2017, 04:03 GMT
I had not idea about that behavior. It helped, yes. Sorry for this incorrect bug report.