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#75443 - [steam] Consider pulling libcrypt.so.1 as dependency
Attached to Project:
Community Packages
Opened by Emil (xexaxo) - Thursday, 28 July 2022, 14:48 GMT
Last edited by Toolybird (Toolybird) - Thursday, 28 July 2022, 22:14 GMT
Opened by Emil (xexaxo) - Thursday, 28 July 2022, 14:48 GMT
Last edited by Toolybird (Toolybird) - Thursday, 28 July 2022, 22:14 GMT
|
DetailsDescription:
As you know somewhat recently glibc pulled out libcrypt.so into separate package - libxcrypt which provides libcrypt.so.2. At the same time a bunch of steam runtime libraries depend on libcrypt.so.1 - see the steam -> help -> system information report for details. Additional info: * package version(s) steam 1.0.0.74-1 Steps to reproduce: - make sure libxcrypt-compat (+ lib32 one) are not installed - launch steam + see the "cannot-load" references, due to missing libcrypt.so.1 - install libxcrypt-compat + lib32 one (from AUR) - launch steam + see nearly all the "cannot-load" references being resolved |
This task depends upon
You can clearly see that nearly all 64bit libraries get happier. While the 32bit ones are still grumpy.
Aside: I'm currently tracking down the final `libitm.so.1` issue, which seems to be Arch specific.
Not sure if steam uses kerberos, but games shipped with steam can. In all fairness if steam flags it as an issue perhaps we should fix it, especially since both size and maintenance are trivial.